How to create a Minimal, Reproducible Example for flow and workflowWhen asking a question about flow or workflow, a support engineer will be better able to provide help if you provide an example that can be easily understood and used to reproduce the problem. The examples should be… …Minimal – Use as few steps as possible that still produces the same problem…Complete – Provide all parts someone else needs to reproduce your problem in the question itself…Reproducible – Test the example you're about to provide to make sure it reproduces the problem The rest of this article provides guidance on these aspects of writing a minimal, reproducible example for flow and workflow. 1, Minimal The more steps there are to go through, the less likely the support engineer can find your problem. Streamline your example in one of two ways: Restart from scratch. Create a new demo, adding in only what is needed to see the problem. Use simple, descriptive names for actions and variables – don't copy the names you're using in your existing item(sub-flows, actions, scripts, etc.).Divide and conquer. If you're not sure what the source of the problem is, start removing items a bit at a time until the problem disappears – then add the last part back. If you think the issue may be caused by an OOTB function, please remove the customized script, objects, tables and etc. as much as possible to ensure that no customized items cover the root cause.It would be very helpful to understand what happened with a clear screenshot based step-by-step guidance. 2, Complete Make sure all information necessary to reproduce the problem is included in the question itself 3, Reproducible To help you solve your problem, others will need to verify that it exists: Describe the problem. "It doesn't work" isn't descriptive enough to help the support engineer understand your problem. Instead, tell other readers what the expected behavior should be. Tell other readers what the exact wording of the error message is, and which line of code is producing it. Use a brief but descriptive summary of your problem as the title of your question.Eliminate any issues that aren't relevant to the problem.Please double-check that your example reproduces the problem. For example, you may inadvertently fixed the problem while composing the example but didn't test it again. Please verify the result before sending it to other parties.