Flow trigger returns HTTP status 202 (Accepted) but nothing happens

Problem

When sending a payload to my flow through the trigger URL it returns an HTTP Status 202 (Accepted) response code, but nothing seems to be happening. Shouldn't this trigger notifications in xMatters?

Environment

All versions of xMatters

Resolution

This usually happens when a flow trigger doesn't have any connected steps. Once you have an HTTP trigger set, xMatters will accept the injection (which is why you will receive an HTTP Status 202 response), but if there are no subsequent steps the flow ends.

Because HTTP triggers always acknowledge receipt with a 202 and a request identifier, you will not see validation or processing failures directly in the HTTP response. To confirm whether an alert was actually created or if the flow encountered an error, you can:

• Use the returned request identifier to look up the resulting alert via the Signals report.

• Review integration or flow logs (or use the integration logs API) to check for mapping or validation errors.

• Set up subscriptions to integration - or workflow-related alerts so you are notified when a flow run reports an error.

Check out our guide on how to design, create, and configure a flow for more information and some helpful tips on building workflows, including how to connect trigger inputs to steps further along in the flow and handle different payload types or status values.