Skip to content
Explore the preview
Browse workflow ideas

Let a long-running task finish before starting it again.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

Before a recurring process begins, check whether its previous run is still active. Wait or skip the new run while work is in progress, then clear its running status after completion or a defined timeout so an operations owner can investigate exceptions without duplicate work piling up.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
Scheduled process checkA scheduled check for a process that should not run in parallel with itself
“Start the selected process only when its prior run is finished, record its running status for a defined period, and make timeouts visible for review.”
Work through the request.

Clear tasks, with review where it matters.

  1. Choose the process and schedule
  2. Check whether an earlier run is active
  3. Record the run and completion status
See all 5 tasks
A recurring process that avoids overlapping runs and leaves timed-out or uncertain cases available for an operations owner to investigate.

What this workflow could do

Helps teams prevent duplicate work and conflicting updates when a scheduled task takes longer than expected.

Review points proposed in this idea

A stale running status can block useful work, while a status that clears too early can allow duplicate runs. Set realistic run limits, confirm that completion and timeout are handled clearly, and give an operations owner a way to review stuck runs before restarting work or changing the schedule.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Identify the recurring work that must run one time at a time and agree on its normal interval.

Step 1 of 5

Choose the process and schedule

Identify the recurring work that must run one time at a time and agree on its normal interval.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Choose the process and run interval

    Select recurring work that must not overlap and set a schedule suited to its expected duration.

  2. 02

    Set the shared running-status record

    Choose a reliable shared place for the process and its scheduled check to read and update run status.

  3. 03

    Define timeout and recovery ownership

    Set a realistic maximum duration and name who investigates stuck runs and approves any recovery.

  4. 04

    Test slow, completed, and interrupted runs

    Confirm a second run waits while work is active and that completed or timed-out status is handled as expected.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation