Runs

Discover the different ways to run an automation process in Kognitos.

Overview

A run represents a single execution of a process. Every time a process is ran, Kognitos captures all the details of its execution (inputs, outputs, and state changes). Each run is also assigned a unique ID, making them easy to track, monitor, and manage.

Ways to Run a Process

All processes can be run manually (draft or published). Published processes can also be triggered to run automatically by email, via API, or on a schedule.

Method
Description
Uses
Process Types

Manual Run

Run directly from the platform by navigating to Processes, selecting a process, and clicking Run to start a new run.

  • Draft

  • Published

Trigger a run by sending an email to a unique email address.

  • Draft

  • Published

Trigger a run by making an HTTP request to the Kognitos REST API.

  • Draft

  • Published

Schedule the process to run automatically at specific times / intervals (e.g., every hour, daily, or weekly)

  • Published

Run States

Runs execute asynchronously, moving through the following status transitions: Pending → Running → Succeeded, Failed, or Cancelled. Once a run completes successfully, its output becomes available for review or use in subsequent actions.

State
Description

Pending

Run is queued for execution.

Running

Run is currently executing.

Succeeded

Run completed successfully.

Failed

Run encountered an error.

Cancelled

Run was cancelled by user.

TimedOut

Run exceeded maximum execution time.

Managing Runs

Once a process has been executed, you can manage individual runs through various actions. To access these options:

1

From the left navigation menu, go to Processes.

2

Select a Process

Click on the process you want to manage.

3

View Runs

Click View Runs to see all the process runs.

4

Select Runs and Choose an Action

Select the checkbox next to one or more runs. The following actions become available:

1. Re-run

Re-executes a process using the same inputs and configuration as the selected run. This is useful for retrying failed runs or reproducing results with identical parameters.

2. Archive

Moves runs out of the main view to help organize and declutter your run history. Archived runs can be restored at any time.

3. Unarchive

Restores previously archived runs back to the main run view. This makes them visible again in the default run list (without filters).

4. Add Test Case

Creates a test case from the selected run. Test cases can be used to validate process behavior in the Test Suite.

Last updated

Was this helpful?