Skip to main content

Executions

An execution is one real run of a process.

If a process is the blueprint, an execution is the actual job being carried out for a customer, request, event, or business case.

This is where the process stops being theory.

Why executions matter​

Executions are where teams answer questions like:

  • What is waiting right now?
  • Who owns the next step?
  • What has already been completed?
  • Did this run fail or get cancelled?
  • What happened for this specific case?

Common execution states​

The app currently supports filters for:

  • Pending
  • In Progress
  • Completed
  • Cancelled
  • Failed

These statuses tell you whether work has not started, is in motion, finished cleanly, or needs attention.

Where you work with executions​

Use the Executions page to:

  • list runs across the workspace
  • filter down to one process
  • search by name
  • sort by created or completed date
  • open a specific execution

A practical mental model​

  • Processes answer: how should this work happen?
  • Executions answer: what happened this time?

This is one of the most important distinctions in Nawfe.

When to open an execution instead of a process​

Open an execution when you need:

  • current status
  • runtime history
  • step-level context
  • troubleshooting on one case
  • proof that a workflow really ran