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.

Check out our guide on how to design, create, and configure a flow for more information and some helpful tips on building workflows.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.