Skip to main content
floo watches for failed deploys and repeating runtime errors. When one fires, it bundles the context and POSTs a JSON event to a webhook URL you configure: an agent, an on-call bot, or an incident pipeline. floo detects and routes; remediation stays with the downstream agent or human.

​
Turn it on

Error routing is off until you point it at a URL. Configure it per app on the dashboard under App → Alerts → Error routing, or with PUT /v1/apps/{app_id}/reparo/config over the HTTP API: There is no CLI command for this configuration. floo events list is the read-only view of what has already fired.

​
What triggers an event

  • runtime errors, repeated error conditions surfaced in logs crossing the configured threshold
  • failed deploys, a deploy that never goes live, rolled back, or exited non-zero
Events are grouped per app. Repeats of the same error roll up into one event, not one per log line.

​
What’s in the payload

Each event carries:
  • what failed (error signature, deploy ID, or log excerpt)
  • recent deploy context (commit SHA, triggered_by, timestamp)
  • X-Floo-Event and X-Floo-App headers, plus X-Floo-Signature (sha256= HMAC of the body) when a signing secret is set
The downstream agent has enough to decide whether to roll back, escalate, or start a fix.

​
Event lifecycle

Each event’s status shows whether your webhook received it:
  • triggered: detected and queued for delivery
  • in_progress: delivery in flight or being retried
  • succeeded: the webhook responded 2xx
  • failed: delivery failed permanently after retries
  • skipped: matched but suppressed (cooldown or rate limit)
List events from the CLI:

​
What it does not do

floo does not generate or merge code fixes. Your agent or on-call workflow owns the fix.
  1. Watch deploy and runtime health.
  2. Let floo create the event and POST it to your webhook.
  3. Your agent or workflow reads the payload, inspects logs and releases, and decides.
  4. Roll back with floo deploys rollback or ship a fix.

Logs and debugging

Runtime logs and deploy history for inspecting the incident further.

Releases and rollbacks

Recover quickly when the right move is shifting traffic back.