Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelogStatus

Workflows Edit

Editing a Workflow​

You can edit a workflow by selecting the row you want from the list of Workflows. From here, you can change the name of the Workflow or Run Workflow Now. This shows monitors that make up the workflow and the variables, if any, that are set at each stage of the workflow. More monitors can be added by selecting the + button on any of the monitors to add one after that call or the Add Step button as well as the Add New Monitor button. The monitors can also be reordered using the arrows on the left of the row and deleted using the bin icon on the right of the row.

Edit Workflow page showing the steps, add and reorder controls, Run Workflow Now, and scheduling

To edit the monitors, select the Edit button to open the individual monitor or toggle the monitor edit mode for a quick edit mode.

Edit Workflow page with the API call edit mode toggle highlighted for quick monitor editing

Workflow in monitor edit mode showing an editable step row with HTTP method, path, auth, and token fields

Running a Manual Workflow​

If you select the dropdown on the Run Workflow Now button, you can choose from the different agents we have available or Google US Central 1 if none are chosen.

Run Workflow Now dropdown open listing agent locations to run the workflow from

Setting Runtime Variables​

Runtime variables can also be set here however, these are temporary and only used at runtime and not during scheduled monitoring. Select Set runtime variables to start.

Workflow configuration with the Set runtime variables link highlighted under Run Workflow Now

Next, select the Add button to create a new variable entry.

Runtime variables panel with the Add button highlighted to create a new variable entry

Next, fill in the variable and value fields, and select the + to add the variable to the runtime variables.

Runtime variables panel with variable and value fields and the plus button to add the variable

Scheduling a Workflow​

Scheduling Workflows is the same process as scheduling an individual monitor. At the bottom of the Workflows Edit tab, you can create schedules for your Workflow and turn on and off different schedules you have created.

Scheduling section at the bottom of the Edit Workflow page with the New Schedule button highlighted

To create a schedule, select the New Schedule button.

Workflow Monitoring section with the New Schedule button highlighted above the schedule cards

A popup will open where you can name your schedule, choose the frequency it runs.

Edit Schedule dialog with fields for the schedule name and run frequency

You can also choose whether you want it to run worldwide or choose from different continents or cloud service providers.

Edit Schedule dialog Node Selection dropdown for choosing worldwide, continents, or cloud providers

If you select the Advanced option, you can fine-tune even further by selecting specific locations.

Edit Schedule Node Locations tab listing individual AWS regions to select specific locations

Finally, you can choose what retry on failure method you would like if any and if you are using the Postman Monitoring feature, you can choose this scheduling here. Once you're happy with your schedule, select the Save changes button and your schedule will be created.

Edit Schedule dialog with name, frequency, worldwide regions, retry methods, and Save changes button

Preventing parallel runs​

A high-frequency schedule or a long workflow can start a new run while the last one is still going. To stop that, open the workflow, select the Advanced tab, and turn on Ensure the workflow does not run in parallel.

With the switch on:

  • One run at a time, everywhere. The lock belongs to the workflow, not to a location, so a run at one location blocks runs at every other location.
  • Every way of starting a run is covered. Scheduled runs, Run Workflow Now, and runs started through the API all check the lock before their first step.
  • A blocked run is skipped, not queued. Its workflow result is marked complete with no steps run. The next scheduled run tries again.
  • The lock ends with the run. It is released when the run finishes.
  • An idle run loses the lock after 5 minutes. If a run has not finished a step for more than 5 minutes (a slow step, or a delay or retry between steps), the next run takes the lock and the two runs overlap. A long workflow keeps the lock as long as it keeps finishing steps.
Best effort

The switch reliably stops runs that start a few seconds apart. Two runs that start at the same moment, for example a schedule that starts the workflow at several locations at once, can both run. To avoid that, schedule the workflow from one location, or space the schedules apart.