Skip to content
Furl Docs

Strategy Executions

A strategy execution is the record of running a remediation strategy on an endpoint. It tracks the full lifecycle from creation through completion, including whether the fix actually worked.

Execution lifecycle

Section titled “Execution lifecycle”
pending → pending_approval → running → succeeded → verified_fixed
                                     → failed
         → blocked
         → preflight_failed
         → rejected
Status Meaning
Pending Created, awaiting dispatch
Pending approval Governance requires human approval before running
Blocked Governance rules blocked execution (blackout window, global pause)
Preflight failed Pre-checks failed (disk space, package manager availability)
Running Executing on the endpoint via the Furl agent
Succeeded Execution completed without errors
Failed Execution encountered an error
Rejected The end user rejected the approval request

Efficacy verification

Section titled “Efficacy verification”

A “succeeded” execution doesn’t necessarily mean the problem is fixed. After execution, Furl verifies whether the finding was actually resolved:

Efficacy status Meaning
Pending Waiting for the next data sync to check
Verified fixed The finding is no longer present
Verified not fixed The finding persists despite “successful” execution
Unknown Unable to verify

This distinction matters: a strategy that runs successfully but doesn’t fix the problem is nearly worthless. A package manager call might exit 0 while the software version doesn’t actually change. Furl detects this and feeds the result back into the strategy’s confidence score — strategies that don’t actually fix things lose confidence over time.

Approval flow

Section titled “Approval flow”

When governance requires approval, the execution enters pending approval and the end user is notified. Approval deadlines are severity-based:

Severity Deadline After deadline
Critical 4 hours Escalated to admins
High 24 hours Escalated to admins
Medium 72 hours Escalated to admins
Low 7 days Escalated to admins

The end user can approve, reject (with an optional reason), or defer (“remind me later”). If no action is taken before the deadline, the request is escalated.

Section titled “Related”