"sys_flow_context" is by default not included in the flow trigger table list, because it can cause loops easily if the trigger condition is not carefully designed.
For example, trigger on "sys_flow_context" record created/updated with no conditions will immediately cause infinite loops and creating huge amount of the flow contexts in the system when triggered. Which will cause high impact outage to the instance.
Resolution Steps:
Add "sys_flow_context" to "sn_flow_designer.allowed_system_tables" system property.
But to trigger flow on flow contexts is not recommended, include the logic in your flow design as subflow should meet the requirements in most cases.
hope this helps you.
I hope this article helpful. Please mark it as helpful and bookmark if you like it.
Regards,
Shamma
