What are the Best Practicies for Workflows in Flow Designer

[Shane Grayson]

Good afternoon, Fellow SNOW Developers,

Our group is seeking advice on best practices for logging in Workflow Designer.

The Problem We Encountered:

We discovered a bug in a workflow associated with a Catalog Item in our Production environment. A flow variable was assigned to Group A under one condition and to Group B if that condition was false. During several executions, the flow variable assigned Group A in the RITM but then assigned Group B in the SCTASK. This was the only place where this assignment occurred, leaving us unclear about what was happening. We checked the Catalog Item for a default support group, which was not present; it did not default to our standard support group when a RITM/SCTASK was created without one. Additionally, there was only one flow variable being assigned the support group in the workflow. This lead us to review the Execution process from the workflow in Production, but it was turned off. (If anyone understands what occurred here, that would be helpful, but this isn't the primary reason for my post.)

What We Would Like to Know:

We brought this issue to our System Admin team and requested justification for why we cannot have Execution Logging in Workflow Studio turned on globally. As we expected, the major concern was that it would be a "resource hog." While we anticipated this response, it raised additional questions that we were unsure how to answer:

1. What resources are actually consumed?
2. Would it have a noticeable impact on the platform if it were turned on globally?
3. What are the ServiceNow best practices for handling logging for workflows?

Thank you in advance to those who respond.

[Uncle Rob]

I'm not the best one to talk resources / performance, but I'm pretty good at flow troubleshooting if you can paste some screenshots of both flow and failure. 

Also, is this replicable in Dev?  Because dev has better logging by default.