Development and Productive Mode
Flow scripts on the Cloudomation platform can be executed in either development or productive mode. The development mode in Cloudomation is intended for use when developing flow scripts. Connections (tasks) in the development mode are free of charge. This means that you can run as many flow scripts as you like with as many connections (tasks) as you like in development mode.
Executions in development mode will only run when you are logged in and active on the platform. Executions in development mode are paused as soon as you become inactive.
We monitor your activity level on the Cloudomation platform using reCAPTCHA v3 which determines your activity level. Once your activity level drops below a threshold, your flow scripts will be paused. You can manually restart paused executions in development mode.
You can also switch executions which you have started in development mode into productive mode. This allows you to test your flow scripts and put them into production directly once you are happy with them. Executions in productive mode count towards your monthly productive connections. Find documentation on how to use the development mode below.
The intention of the development mode is to make it easier for you to develop flow scripts. The development mode gives you the opportunity to explore the Cloudomation platform freely, to experiment and play around. It also allows you to test your flow scripts frequently while developing them. However you should not use the development mode for running flow scripts that you want to use in production. Using the development mode for productive flow scripts is a breach of contract.
- Connections by executions in development mode are free of charge.
- Executions in development mode are paused when you become inactive.
- The development mode should only be used for developing flow scripts.
Using the Development Mode
You can start an execution in development mode manually via the user interface, or via a webhook that is configured to start executions in development mode. Executions started in development mode can start other executions which will automatically also be started in development mode.
Executions can be started in development mode by pressing the “Try” button in the user interface. Running executions with the “Run” button will execute them in productive mode.
Executions can also be started in development mode via a webhook. To configure a webhook to start executions in development mode, add the line
mode: dev to the setting that configures the webhook. If no mode is specified in a webhook setting, all executions will by default be executed in productive mode.
Executions in development mode are highlighted with a warning triangle in the executions view:
You can switch executions which are in development mode into productive mode. To do this, open the details view of the execution and press “switch to productive mode”:
The “is productive” field in the executions details view always shows if an execution is running in development or in productive mode: