Runs

Each time Rewst does something, we call this singular event a run. View and manage execution runs from the Runs section of the left side menu. You can also view a snapshot of recent runs from the Rewst Dashboard.

The Runs list screen with recently executed workflows

The Runs page

The run records are divided by type, via tabs at the top of the page.

• Workflows - This contains each record of every one time execution of a workflow, from start to finish.

• Fabric - Fabric is Rewst's internal system for talking to your other tools. A fabric run is a single request to one outside system. While a workflow run has man steps, a fabric run is a single action and much more straightforward to view. Look here when you suspect that the connection itself is an issue, like an expired password or a partnered system outage.

• Called by Child - These are runs of workflows called by other workflows, also known as subworkflows.

• All - This displays every type of run in one list.

The Status column indicates the status of the run: Pending, Running, Queued, Completed, Failed, Timed out, Canceled, and Terminated. Filter any of the statuses by type to narrow down your list.

The Workflow column lists the name of each workflow, as well as its publication status and indicators for if the workflow runs on a cron schedule and is currently live.

The Started and Finished columns display the start and end times for the workflow's run. The total time for the run is displayed in the Duration column.

The Tasks column lists how many tasks executed in the workflow.

If there was an error during the run, the Error column will display a short summary message explaining what failed.

Individual run results

Click into any of the runs to view its details.

• Click View on Canvas to open the workflow in the Workflow Builder.

• Click Rerun to trigger an immediate additional run of the workflow.

• Click Context to open the run result in relation to its context variables.

• The three view tabs at the bottom of the page show the same run data, but they differ in what dimension they organize it by: structure, time, or text.

  • Flow is the default and the one to start with for questions concerning correctness. It answers routing questions instantly. Click a node to inspect that node's input, output, and context for the run.

  • Timeline is the performance and concurrency view. Steps become bars positioned by when they started and sized by how long they took, so a slow HTTP call or a retry-with-backoff stands out immediately, and genuinely parallel branches visibly overlap rather than appearing merely adjacent. It's also the clearest way to see that a loop actually iterated N times, and how the cost was distributed across iterations.

  • Log is the text-first, high-volume view. It's the fastest way to scan a long run top-to-bottom, find the first failing step rather than the last one, and copy an exact error string. For runs with hundreds of steps, this is usually faster than clicking around the graph. Click to expand each item and view the related code.