Catalog request is cancelled automatically for end-user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Hi,
I created a catalog item. When I test it as an admin, it works: the flow is triggered: approval, etc
But when I impersonate an end user, the request is cancelled automatically.
I verified that the end user's profile has a manager.
One thing that I suspect is the flow properties: Run as: User who initiates session.
When I change that into: System User. it works
However, in Test environment, the flow Properties is set to: User who initiates session, and the flow works.
Any insight into this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
so approval is not triggering when non-admin raises request?
what's the error?
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
well what happens is that when I open the request its stage is: request cancelled
These are the error logs:
Flow execution is cancelled upon receiving request. Reason is: Aborting engine execution, cancel requested in same txn in which flow is running
And this warning: skipped due to no valid approvers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
ensure you keep flow always as Run as -> System User
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
56m ago
Hi @hamidouche ,
Please check below following area:
1. Check Flow execution when impersonating end user which error is throwing .
2. Check Request item activity - state change history, system log.
3. You can add error handling mechanism or add log message to track issue.
4. As a best practice Run as "System Admin".
5. Please check in Test instance, impersonated user has any extra role.
Please mark helpful and correct answer if it's worthy for you.