Executions are a journal of the results of your experiment run. Each time one of your experiments is run as part of a plan, an execution is generated and available in Reliably. It presents the execution’s results and allows you to download a complete execution journal.

A screenshot of an execution page in Reliably.

Execution info

At the top of the page is displayed the execution’s unique UUID, as well as some general information about the execution:

  • its status (here, our experiment deviated, meaning its result was not what was expected),
  • when it ran,
  • the name of the experiment (here, Latency remains under 200ms, which is one of our starters).


This section displays:

  • the execution status,
  • if the execution deviated,
  • when the execution started,
  • when the execution ended,
  • the execution duration.

It also presents links to:

  • the execution journal,
  • the execution logs,
  • the GitHub workflow page, if it was run as a GitHub Action


This section presents information about the environment the Reliably experiment was run in.

  • ChaosLib is the version of the Chaos Toolkit Library used,
  • Platform is the Operating System that was used,
  • Node is the name of the machine the experiment was run on.


This Reliably timeline is a step-by-step breakdown of all the events that took place during an experiment execution.

It displays the main phases of the execution (steady-state hypothesis, method, rollbacks) as well as each activity that took place.

If an activity returns a result, this result is displayed in the event.

A screenshot showing two events in a timeline. The first event is the end of a probe activity. The probe is named measure-endpoint-response-time, and we can see it's tolerance was not met. The next event is the end of the steady-state hypothethis. It tells us the steady-state was not met, which is a consequence of the previous probe's tolerance not being met.

Some activities, such as probes, can return more detailed results. If this is the case, a “Details” button reveals those results.

A screenshot showing the same first event as on the previous screenshot. The details section is opened and reveals the probe was successfully run, but it returned a value of 0.39 seconds, which is above the expected threshold of 200 ms