Ruvix

Pause & Resume ​

You can pause a running workflow and resume failed or partially successful executions.

Pausing an Execution ​

To pause a running workflow:

  1. Open the execution detail page (or watch it in the builder)
  2. Click the Pause button
  3. The workflow pauses between node executions — the currently running node will finish, but no new nodes will start

The execution status changes to Paused.

INFO

Pausing is graceful — it doesn't interrupt a node mid-execution. The current node completes, and the workflow pauses before scheduling the next node.

Resuming an Execution ​

You can resume executions that are in one of these states:

  • Failed — one or more nodes failed
  • Partial success — some nodes succeeded, others failed

To resume:

  1. Open the execution detail page
  2. Click the Resume button
  3. The workflow picks up from where it left off

How Resume Works ​

The platform uses checkpoints to track progress at the node level:

  • Nodes that already completed successfully are not re-run
  • Failed nodes are retried from their last checkpoint
  • Pending nodes that haven't run yet will execute normally

This means you can fix the underlying issue (e.g., update a connection's credentials, fix a remote server) and then resume without re-processing data that was already handled.

WARNING

Only the most recent execution can be resumed. If a workflow has been run again since the failure, the older execution cannot be resumed.

24-hour resume window

Checkpoint data — the per-node progress used to resume without re-processing items — is retained for 24 hours after an execution pauses or fails. After that, attempting to resume returns an error (checkpoint_expired) so we don't silently re-run nodes that already had side-effects (sent emails, inserted rows, called external APIs).

If you need to act on a >24h-old failed execution, run the workflow again instead of resuming — that gives you a fresh execution and avoids partial reprocessing.