Script written inflow designer not working in TEST whereas working fine in DEV and PROD

[SaiUpeshJ]

The code which has been written in the  flow designer is not working in Test environment but is working in dev and Prod environment. What could be the issue? Any suggestion on that.

[Mark Manders]

We can't suggest much, since you shared absolutely nothing. You didn't share the script, you didn't share the flow, you didn't share the results from the flow executions.

So let me answer your question 'what could be the issue': your flow testing on the test instance didn't meet the conditions, hence wasn't fired and the script didn't do a thing.
I can give you hundreds of similar answers that don't help you, because I have to guess everything about your question.

[Tanushree Maiti]

Hi @SaiUpeshJ 

•  Open Flow Designer directly in the Test environment and look at the top right header. Ensure that the flow status reads Active. If it says Draft, click Publish
• Look at the Update Set Preview Errors in Test to see if anything was skipped. If needed, re-capture the flow or actions in a new update set from Dev by making a minor cosmetic change and migrating it again
• If your main flow references a subflow or a custom Action, and that action wasn't included in the update set or failed to commit, the main flow will error out with "Action not found"
• Refer: "Your flow cannot be found. Flow sys_id:An" error 
• Does your flow filter by a specific User, Assignment Group, or CI? If that record does not exist in Test—or exists but has a different sys_id, the condition will fail silently or crash
•  

[joshuajacks]

@SaiUpeshJ 

To emphasize what Mark mentioned, context would be helpful. There could be any number of things to make it "not work" but here are a few possibilites:

• The flow is running as the "user who initiates" the session rather than the system user and dev you may have admin access but in test or prod you don't and the user's triggering the flow don't have sufficient access to do what the flow is doing.
• There could be some artifacts from the flow that were not captured properly in the update set.
• There could be version differences between the workflow studio app in each environment.
• An update to workflow studio could have changed how data is handled. (We recently had a situation after our upgrade where a true/false catalog variable used to be 0/1 within the workflow but now is true/false)

As suggested, test the flow action and/or flow within workflow studio and use the errors to troubleshoot.