How to monitor and manage your workflows

Draft vs. Published

Every workflow has two states:

When you open a workflow you've previously published, you see the draft — your editable working copy. The published version runs in the background until you click Publish again to replace it.

Two important toggles:

• Publish — promotes your draft to live. Required after any change.
• Active / Paused — turns the workflow on or off entirely without changing its configuration. Useful for temporary stops (e.g., during a Monday.com migration).

A workflow can be Published but Paused — meaning your configuration is saved as the live version, but no executions will run until you re-activate it.

Viewing recent executions

Navigate to Admin → Workflows → [workflow name] → Runs.

You'll see a table of every execution, most recent first. Each row shows:

Click any row to expand the full execution detail.

What's in an execution detail

For each run, you can inspect:

1. The full trigger payload — exactly what Marq sent to your workflow. Useful for verifying that the data you expected actually arrived.

2. Per-node execution status — green/red indicators showing which steps succeeded. Click into a node to see:

• Inputs (the data passed in)
• Outputs (what the step produced)
• API requests made (for connector actions)
• Error messages if it failed

3. Created resources — links to anything the workflow created downstream (e.g., the Monday item ID, Asana task URL).

Filtering and search

Above the executions table:

• Date range filter — Last hour / 24h / 7 days / custom
• Status filter — Show only failures, only successes, etc.
• Search — find runs by trigger field (e.g., project title contains "Q1")

Troubleshooting failed runs

When a run fails:

1. Click the failed run to expand details.
2. Find the red node — that's where execution halted.
3. Click into the node to see the error message and the inputs that caused the failure.

Common failure patterns:

Retrying a failed run

Open the failed execution → click Retry. Marqet replays the run using the same trigger payload. Useful when the failure was transient (e.g., the connector was briefly down).

Pausing a workflow

To temporarily stop a workflow without losing its configuration:

1. Navigate to the workflow.
2. Toggle Active to off (or click Pause in the top bar).

The listener stops receiving events — incoming triggers are dropped, not queued.

To resume: toggle Active back on. New events will start flowing again.

Editing a published workflow safely

The recommended flow for changes to a live workflow:

1. Open the workflow — you're now editing the draft.
2. Make your changes.
3. Test Run against a sample or recent real event.
4. Confirm the test succeeds.
5. Click Publish to promote the draft.

During editing, the previously published version keeps running. Your changes only go live when you publish.

Warning: If you need to change a connector's credentials (e.g., rotating a Monday token), do it during a low-activity window — in-flight executions may briefly fail while the new credential propagates.

Deleting a workflow

To permanently remove a workflow:

1. Toggle it to Paused first (best practice — ensures no in-flight runs).
2. Open the workflow's Settings tab.
3. Scroll to Danger zone → Delete workflow.
4. Confirm by typing the workflow name.

Deletion is permanent. The webhook is unregistered from Marq, and execution history is retained for 90 days after deletion before being purged.