- Once you start a connector its status is always in draft. In this status you can build, debug and test it. Once ready, set the status to live. In this status the scheduler will actually schedule and execute flows. This is not the case in draft or paused. So the status live should always be used for all actively running flows. If a flow throws multiple errors or you want to actively prevent it from executing use the status paused. You can change the status either in the upper left corder of the FlowBuilder by clicking on the button:
or by clicking on the edit button:
- Reduce the flow in its components and try running (debugging) one step at a time rather than building everything at once. Once the first steps work, add in more functionality.
- Use test-data sets initially that are rather small, just to test functionality of each step properly. For CSV, XML or JSON-files you can e.g. upload test data to AWS S3, Google Drive or Dropbox and use them. If you query a REST API, try filter e.g. by date range to keep the flow small.
- Look at other flows you already built or you can find in the Flow Template Marketplace Flow Template Marketplace.
- If you send emails, only send them to your self for testing purposes.
- If you need more space, you can ZOOM in and out by pressing the CMD button on a Mac and the CTRL button on a PC and zoom in or out with your mouse.
- You can copy individual connectors just by CMD + C and CMD + V after clicking on a connector. It will copy it including all its settings.
- Once a flow is ready to run, include email addresses you want to be informed if an error occurs for any reason on the Flow Builder edit dialogue, comma separated.
What are the best practices of flow building and testing? Print
Created by: Richard H
Modified on: Tue, 10 Sep, 2019 at 7:48 PM
Did you find it helpful?Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.