Problem with executing an Action in SAP Build Process Automation

[AdrDen]

Hi,

We have a problem with executing an Action in one of our processes. It ends with error message: Action 'daa781da-321c-4585-b5ef-e097724206aa' failed with the following error: '503 Service Unavailable'.

Details:

- Our Destination called gateway_Z_EMPLOYEES_SRV points directly to OData Service exposed in our Gateway on-premise system. The URL is http://<gateway loction>/sap/opu/odata/sap/Z_EMPLOYEES_SRV. We use PrincipalPropagation as authentication method. We also added some additional properties: AppgyverEnabled (true), sap.applicationdevelopment.actions.enabled (true), sap.build.usage (odata_gen), sap.processautomation.enabled (true). Cloud Connector is exposing /sap/opu/odata with all sub-paths.

- We have Actions project, where we added a new Action called Get Employee by key. It's a simple GET_ENTITY call. When Testing directly in the project using gateway_Z_EMPLOYEES_SRV, the thing works, and we receive the data from the system.

When it comes to URL Prefix part, we have left it empty (our destination is pointing to specific Service).

When it comes to our Action Project Settings, we have enabled CSRF, and the Token Fetch End Point is "/".

Here I'm not sure if both settings are correct.

- Our Process is simple. We have a trigger form with Employee ID input, which is then passed to our Action as GET_ENTITY key.

We have created a Destination variable called employee_conversion_process_destination. While Releasing and Deploying the project, it was set to gateway_Z_EMPLOYEES_SRV.

- We use generated trigger Form Link after deployment to test the Process.When we access Process and Workflow Instances (Monitor tab), we see our Process is in status Error. Details say the Service is Unavailable.

Any ideas what could be the issue?

BR,

Adrian

[TJe · Accepted solution]

You mentioned you are using Principal Propagation.
Did you specify Run step on behalf of parameter on the action in your process ?

[AdrDen · Accepted solution]

Thanks thomas.jentsch, it helped.

We weren't aware this setting needs to be maintained.

By using Process Start as on behalf it started to work. Thanks a lot again!