Catalog item - Request cancelled for end user

[PriyangaM]

Spoiler

Spoiler

I am building a catalg item with flow designer (decision table) , as admin i can submit request and works as expected when end user submits a request it is getting cancelled automatically  without triggering approval it automatically checks else condition and cancells.

Looking for some insignts  

Spoiler

[Maham Tahir · Accepted solution]

Hi @PriyangaM, 

Can you please share your decision table logic? It'd be easy to identify the issue if you do so. 

Plus, you can check the roles as well as decision table needs extra roles and maybe you as admin have these roles and end users don't have.

You can see the roles here:
Configuring decision tables

If you find my response helpful, mark it as helpful and accepted solution.

Regards, 

Maham Tahir.

[CN-L · Accepted solution]

Under 'additional properties', is your flow set to run as 'User who initiates session' or 'System user'?

[Maham Tahir · Accepted solution]

Hi @PriyangaM, 

Can you please share your decision table logic? It'd be easy to identify the issue if you do so. 

Plus, you can check the roles as well as decision table needs extra roles and maybe you as admin have these roles and end users don't have.

You can see the roles here:
Configuring decision tables

If you find my response helpful, mark it as helpful and accepted solution.

Regards, 

Maham Tahir.

[CN-L · Accepted solution]

Under 'additional properties', is your flow set to run as 'User who initiates session' or 'System user'?

[Me Being Mustaq · Accepted solution]

Hi @PriyangaM ,

When the catalog request works for admin but auto‑cancels for end users, it is almost always because the Flow / Decision Table hits an error or “no match” path for end users (roles/permissions/data), so the Flow goes through the else branch that cancels the RITM.

Most likely it causes:

• Decision table roles / data mismatch
• Missing access to referenced data
• Flow error handling configured to cancel

Recommended fixes

• Give the correct roles to the Flow runner

• Handle “no match” more gracefully
• Test with a non‑admin use

If you share a simplified screenshot / description of your decision table (inputs and rows) and the Flow’s else branch, a more concrete condition or script to avoid the unwanted cancellation can be suggested.

If it is helpful, please hit the thumbs button please mark the answer as correct based on the impact!!

Kind Regards,

Shaik Mohammed Mustaq