> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage workflows

> The workflows list, runs, version history, settings, permissions, and templates.

Everything that happens after the canvas: monitoring runs, keeping order in the list, controlling versions, and sharing your work.

## The workflows list

The Workflows page shows every workflow with its status, trigger (and live version), folder, and last run. Tabs filter by state — **All, Active, Paused, Drafts, Ready** — and you can search or filter by creator and folder. A **Draft changes** badge marks published workflows with unpublished edits; **Needs attention** marks workflows with an issue.

Row actions (availability depends on your [access level](#permissions)):

| Action         | What it does                                                                                  |
| -------------- | --------------------------------------------------------------------------------------------- |
| Edit           | Opens the editor. Clicking the row opens Runs for published workflows, the editor for drafts. |
| Duplicate      | Copies the workflow and opens the copy as a new draft.                                        |
| Move to folder | Organizes workflows into folders.                                                             |
| Pause / Resume | For scheduled workflows: stops or restarts the cadence without touching the definition.       |
| Delete         | Permanent, with confirmation — it also cancels any ongoing runs.                              |

<h2 id="runs">
  Runs
</h2>

Every published workflow has a **Runs** tab: a day-grouped list of runs on the left, the executed graph on the right.

* **Starting a run** — manual-trigger workflows have a **Run workflow** button (it prompts for the contact/company list if the trigger asks at runtime). Webhook workflows show **How to run** with the URL, secret, and example body; intent-triggered workflows simply show they're active and run on events.
* **Run statuses** — Running, Completed, Stopped (e.g. by a credit limit), Failed, Cancelled.
* **Inspecting a run** — the graph highlights executed steps; click any step for its detail panel: inputs, outputs, per-contact/company outcomes, processed counts, and the error with stack trace if the step failed.
* **Cancelling** — a running run can be cancelled from the panel. Work already dispatched in the background may still complete and spend credits.
* **Skipped records** — with "Process each contact only once" enabled ([settings](#settings)), records handled by a previous run are skipped and counted on the run card.

There is no automatic notification for failed runs — check the Runs tab (or the Activity page) after important executions. See [Troubleshooting](/workflows/troubleshooting) for reading failures.

<h2 id="version-history">
  Version history
</h2>

Publishing creates an immutable version. From the editor's **Version history** drawer you get a timeline of publishes, restores, setting changes, and draft saves — each publish can be **viewed** (read-only render of that version's graph) or **restored as draft**.

Restoring replaces your draft with the old version; **the live published version keeps running until you publish again**. The Settings → History tab lists every published version with who published it, its trigger, and whether it's the live one.

<h2 id="settings">
  Settings
</h2>

The **Settings** tab of a workflow:

| Setting                    | What it controls                                                                                                                                                             |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Run credit limit           | Caps how many credits a single run may spend. A run that would exceed the cap stops *before* the step that would go over budget, with the budget and spend shown on the run. |
| Contact enrollment         | "Process each contact only once" (recommended for recurring workflows — no repeat outreach or double credit spend) versus reprocessing everything on every run.              |
| Create a reusable template | Turns the published workflow into a template — with a name, description, and an optional share toggle for your workspace.                                                    |

<h2 id="permissions">
  Permissions
</h2>

Workflows carry per-workflow access control, managed in Settings → **Permissions** (visible to users with Full access):

* A **workspace default** access level for everyone, plus per-member grants.
* Levels: **No access**, **Read only**, **Read and write**, **Full access**.
* Editing needs read-write; duplicating, pausing, deleting, and managing permissions need higher access. Read-only users see Settings dimmed with a "Read only" badge.

<h2 id="templates">
  Templates
</h2>

The templates gallery (**My templates** / **Enginy templates**) is the fastest way to spread working patterns across the team:

* Each card shows the trigger type, step count, and tags, with a **Preview** of the full graph before committing.
* **Use template** creates a new draft from it and opens the editor.
* Create your own from any published workflow via Settings → Create template; share it to make it available to the whole workspace.

## Next steps

<CardGroup cols={2}>
  <Card title="Troubleshooting & credits" icon="triangle-exclamation" href="/workflows/troubleshooting">
    Reading failed runs and how credits are spent.
  </Card>

  <Card title="Create your first workflow" icon="hammer" href="/workflows/building">
    The path from blank canvas to published.
  </Card>
</CardGroup>