Runs

A run is one durable execution of a Loop. The workflow runtime advances the graph, while Fondaro keeps the run and per-node state as the product history.

Open the Loop editor to follow both live and historical runs.

Run and node states

A run can be:

• Queued while accepted and waiting to start;
• Running while at least one node is working;
• Awaiting input while suspended at a human review or approval checkpoint;
• Completed when every reachable node has settled;
• Failed when a node failure prevents the run from finishing;
• Cancelled after a user cancels it.

Each node has its own pending, running, awaiting input, complete, skipped, or failed state. If an upstream node fails, dependent nodes are marked Skipped instead of running with missing input.

Watch a live run

The editor refreshes the active run while it is live. Select a node to inspect its timestamps, input, output, AI narration, refusal, error, or skip reason. With no node selected, the run summary shows how many nodes have settled and how many are awaiting, failed, or skipped.

The recent-runs strip at the bottom includes manual, scheduled, and event runs. Select an older run to put the graph into read-only history mode. Return to the live draft before editing again.

If your Fondaro deployment exposes an operator trace link, the run summary can open that workflow trace. Fondaro's own run records remain the lasting history even after an external trace expires.

Human review

At a Human review node, select the rows that should continue, then choose the continue action. Choose Skip all when none should proceed.

The run is durably suspended while it waits. You can close the browser and return later without losing the selection point.

Human approval

At a Human approval node, decide each persisted proposal:

1. Open a proposal and review the target and payload.
2. Edit the supported fields if needed.
3. Choose Approve to execute that proposal or Dismiss to leave the CRM unchanged.

Bulk approve and dismiss use the same decision rules. Each decision is saved immediately. After every proposal has a decision, Fondaro resumes the run automatically.

Retries cannot create a duplicate proposal or repeat a completed write because workflow writes use deterministic replay protection.

Failures

Transient workflow steps are retried up to three times. A rate-limited step can wait until a later retry, while a permanent validation problem fails visibly.

If a node remains Failed, select it and read the error. Fix the graph, configuration, entitlement, or source data, then start a new run. The current UI does not restart an individual failed node inside the same run.

Large per-lead branches are split into independent child workflows. A retry for one lead does not repeat writes already completed for another lead.

Cancel a run

Choose Cancel run from the run summary while the run is live. Cancellation prevents later graph steps and new CRM writes from starting. A request that had already reached an external service may finish before cancellation is observed, so inspect the final node and CRM state after cancelling.

Cancelling a run does not pause or delete the Loop. If the Loop remains active, a later schedule or event can start another run.

Delete a Loop

Deleting a Loop permanently removes the Loop and its run history. This cannot be undone. Pause the Loop instead when you only want to stop new automatic runs.