Resolve inactive flows for requested items

Understand what causes a requested item (RITM) flow to not start after the request is approved, and how to resolve it. 

When a RITM stage changes to request_approved, the flow fails to start and generates the following error in system logs, which show a FlowObjectAPIException indicating the flow has not been published : 

com.glide.plan.runners.FlowObjectAPIException: The flow named: <flow_display_name_here> has not been published within application scope: global
Caused by error in sys_script_include.8f3a2778c0a8002700fbde5ad148abe3.script at line 54
com.glide.plan.runners.PlanRecordRetriever.getPlanRecord(PlanRecordRetriever.java:49)
com.glide.plan.runners.FlowObjectInstanceFactory.createFlowObjectInstance(FlowObjectInstanceFactory.java:23)
com.glide.plan.runners.scriptable.ScriptableFlow.jsStaticFunction_startAsync(ScriptableFlow.java:40)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
...

Any supported release

This issue occurs when:

• The flow is deactivated in Flow Designer.
• The active flag on the sys_flow_catalog_trigger table is set to false.
• The service catalog business rule tries to launch the catalog item flow when the RITM stage changes to request_approved.

To resolve this issue:

1. 1. Go to Flow Designer.
   2. Open the inactive flow.
   3. Select the Activate button to publish the flow.