Error for subflow: com.snc.process_flow.exception.ProcessAutomationException: invalid context id

[peter_repan]

Dears,

I have a Service Portal widget, calling in Server-side script sub-flow:

sn_fd.FlowAPI.getRunner().subflow('<subflow name>').inBackground().withInputs(<params>).run();

I am getting error com.snc.process_flow.exception.ProcessAutomationException: invalid context id and have no idea from where it's coming. 

Does anybody have experience with such error and can help please? 

[Sumanth16]

Hi @peter_repan ,

Please refer to below threads:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0854540

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0820823

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda

[peter_repan]

The issue was caused by out of the box role snc_read_only.

Testing user has this role and because of that, Subflow could not create context record. 

[Aqib4]

Hi @peter_repan,

The error message "com.snc.process_flow.exception.ProcessAutomationException: invalid context id" typically indicates an issue with the context in which the Flow Designer subflow is being executed. This error often occurs when the context is not properly initialized or when there's an issue with passing parameters to the subflow.

Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Check Subflow Configuration**: Ensure that the subflow you are calling (`<subflow name>`) is configured correctly in Flow Designer. Make sure that all required input parameters are defined and that the subflow is designed to handle the inputs you are providing.

2. Verify Input Parameters**: Double-check the input parameters you are passing to the subflow using the `withInputs()` method. Ensure that the parameters match the expected types and formats defined in the subflow.

3. Review Context**: Check if there are any dependencies or context requirements within the subflow that might not be fulfilled when it's called from the Service Portal widget. Sometimes, certain contexts are expected to be present, and if they're missing, it can lead to errors.

4. Debugging**: Add logging statements or try-catch blocks in your server-side script to gather more information about the error. Log the input parameters, and any intermediate steps to see where the error might be occurring.

5. Test in Flow Designer**: Test the subflow directly in Flow Designer to ensure that it runs successfully with the provided input parameters. This can help isolate whether the issue lies with the subflow itself or with its invocation from the Service Portal widget.

6. Check System Logs**: Review the ServiceNow system logs for any additional error messages or stack traces that might provide further insights into the cause of the issue.

7. Engage ServiceNow Support**: If you're unable to resolve the issue on your own, consider reaching out to ServiceNow Support for assistance. They can provide guidance and help troubleshoot the issue further, especially if it's related to platform-specific behaviors or configurations.

By following these steps, you should be able to identify the cause of the "invalid context id" error and take appropriate actions to resolve it.

Please hit helpful and accept this as a solution if solves your queries.

Regards: Raja Aqib