Flow is not triggering

Yd0801 · yesterday

There is a flow which is attached to catalog item , the flow was triggering properly, but today when submitting the catalog item the flow did not triggered, it is active and published. When i am clicking TEST in flow then the flow is working. Does anyone have idea why it is happening?

Matthew_13 · yesterday

I have seen this happen I believe when the flow itself is fine, but the trigger conditions arent matching at submit time which is why it still works when you clicck Test.

A few common things I say you to check:

Trigger table and conditions – Confirm the flow is triggered on the correct table (most often Requested Item) and that any conditions still match the data being created when the catalog item is submitted. Even a small change to the item, variables, or conditions can stop the trigger from firing.
Timing of field population – If the trigger is set to Created and depends on variables or fields that are populated after insert, the flow won’t start. In those cases, using “Created or Updated” with a guard condition often resolves it.
Flow executions – Go to Flow Designer → Executions and check around the submission time.
- If there’s no execution at all, the trigger didn’t match.
- If there is one, open it to see whether it was skipped, canceled, or failed immediately.
Item or version changes – Verify the submitted catalog item is the same one the flow expects (no clones, new versions, or sys_id changes), and that you’re looking at the published version of the flow.
Submission path differences – Submissions via a different portal, order guide, or integration can populate fields differently than expected, causing the trigger to miss.

At the end of the day, I say the flow working in Test tells you the logic is fine; the issue is almost always that the real submission data no longer meets the trigger conditions at runtime. If that don't work send a screenshot.

@Yd0801 - Please mark as Accepted Solution and Thumbs Up!!