Hi @GannahA
This behavior is actually expected and usually comes down to how Flow Designer runs during testing vs real execution.
When you test a flow in Flow Designer, it runs with elevated permissions, so ACLs and cross-scope restrictions are bypassed. When the same flow runs in real time (when the RITM is actually closed Complete), it runs under normal system context and all ACLs apply. Because the Policy Exception table is part of GRC, write access is heavily restricted, which is why the record is not being created.
There are also two other common causes to check:
1. Trigger vs Wait condition
If your flow is:
Trigger → Wait for condition → Create Policy Exception
The wait condition may never resume. In many cases, the RITM state changes to Completed before the flow reaches the wait step.
Recommended approach:
Use the trigger condition State changes to Completed on sc_req_item and remove the Wait condition entirely. This avoids timing issues.
2. ACL / Cross-scope access
Even if the trigger fires correctly, the flow can silently fail when trying to insert into the Policy Exception table.
To confirm:
Check System Logs > All and filter for:
Source = Flow Engine
Level = Error
You will usually see an access or cross-scope error.
Create a Script Include in the GRC scope that inserts the Policy Exception record, and call that Script Include from the flow. This is the safest and supported approach for GRC tables.
*************************************************************************************************************
If this response helps, please mark it as Accept as Solution and Helpful.
Doing so helps others in the community and encourages me to keep contributing.
Regards
Vaishali Singh
