CAP to BPA Trigger: API returns instance ID, but completely missing in Monitoring/Inbox (Shared Env)

[#1]

Hi everyone,

I'm facing a weird issue triggering an SAP Build Process Automation (BPA) workflow from my CAP backend.

Everything worked perfectly when the BPA project was deployed in the default Public environment. However, after undeploying and moving it to a newly created Shared environment, the workflow silently disappears.

Here is what is happening:

• I updated the endpoint URL for the new environment.

• I generated a new API Key (irpa-api-key) with the required scopes and passed it in the CAP request headers.

• The CAP POST request is successful—it returns HTTP 201 and I get a valid bpa-instance-id logged in my console.

• The Issue: The workflow never arrives in "My Inbox". Furthermore, when I search for the exact instance ID in the BPA Monitoring dashboard, it says "No data" (even with all filters like 'Started By' cleared).

Since the API returns an instance ID, the payload is clearly reaching the BPA server. Why is the instance vanishing before it hits the monitoring dashboard or inbox? Could this be a payload schema mismatch in the new environment, or some hidden routing issue?

Any pointers would be hugely appreciated!

Thanks,

Anurag

[RanjeetKr · Accepted solution]

Hi Anurag,

A 201 Created response with an instance ID only confirms that the workflow start request was accepted by the API. It doesn't necessarily mean the workflow instance was successfully created and persisted.

A few things I'd check:

• Verify you're looking at the correct environment/tenant. After moving from the Public environment to a Shared environment, it's easy to accidentally monitor the wrong environment.
• Confirm the API endpoint matches the Shared environment. The endpoint, API key, and workflow deployment should all belong to the same environment.
• Check the API key and service instance. Even if the key has the required scopes, make sure it was generated for the Shared environment and not the previous Public environment.
• Ensure the workflow is deployed and released in the Shared environment, and that you're using the correct workflow definition ID.
• Look for execution logs in SAP BTP (Build Process Automation, Audit Logs, or Cloud Foundry logs if applicable) to see whether the instance is failing immediately after creation.
• Validate the start payload against the workflow's expected input schema. Some validation failures can cause the instance to terminate before it becomes visible in Monitoring or Inbox.

A couple of questions that may help narrow it down:

1. Are you using the same subaccount with a different environment, or a completely different subaccount?
2. Are you calling the Workflow Runtime API for the Shared environment?
3. If you start the workflow manually from the BPA UI in the Shared environment, does it appear in Monitoring and My Inbox?

If manual starts work but API-triggered ones don't, the issue is likely with the endpoint, authentication, or request payload rather than the workflow itself.