Flow desiginer is not triggering after adding in catalog item form flow field

[AzizM]

I configured the Service Catalog as the trigger condition for the flow. However, the flow is not triggering when a request is submitted, and no Flow Context is being created for the RITM. When I test the flow directly from Flow Designer, it executes successfully. Am i missing something?

[Vishal Jaswal]

Hello @AzizM 

Navigate to All > Maintain Items and enter the name of your catalog item.
Scroll down to Process Engine tab and select the desired Flow.
Hit Save/Update.

[CN-L]

Hi @AzizM,

It's difficult to advise without being able see your flow however a couple of things to check would be

1. who the flow is set to 'run as'? (System User or User who initiates session)
2. has the flow been activated?
3. has the flow been linked to the specific catalog item?

If you're able to share a screenshot of your flow, that would help with troubleshooting.

[AndersBGS]

Hi @AzizM 

I think you need to provide some additional context before we can help with your question. Please provide some screenshots etc. to get the help needed.

[kmohammed]

Hi @AzizM,

You are most likely missing the link between the flow and the catalog item — the trigger alone does not do that.

A Service Catalog trigger says when a flow may run, but the flow only runs for a catalog item when it is also selected on that item: All > Maintain Items > your catalog item > Process Engine tab > Flow. If that field is empty, no Flow Context is ever created for the RITM — which matches exactly what you are seeing. Testing the flow directly from Flow Designer works because the test runs the flow standalone and bypasses the catalog item link, so a successful test does not prove the wiring.

Check these, in order:

1. Maintain Items > your item > Process Engine tab — is your flow selected there?

2. Is the flow Active? A saved but inactive flow never triggers.

3. Does the trigger match the RITM that is created? The Service Catalog trigger is on the Requested Item [sc_req_item] table — check its conditions actually match the item being ordered, and that the flow and the catalog item are in the same application scope.

4. Then check Flow Designer > Executions for the RITM. If there is no execution at all, the flow never started (points 1-3). If there is an execution with an error, the problem is inside the flow, not the trigger.

The first check is the one that catches most people — the trigger and the Process Engine link are two separate things, and both have to be in place.

If this helped, please mark it as Helpful — and if it solved your issue, I'd be grateful if you accepted it as the solution.