doctor

floo doctor returns one verdict plus the evidence behind it. Every doctor command supports --json and exits non-zero when it detects an issue, so agents can branch without parsing output.

push

Explain why the last git push did or did not deploy, and what to do next:

floo doctor push
floo doctor push --app my-app
floo doctor push --json

The last push to main (3f9c2a1) at 2026-10-27 22:12 UTC was skipped because deploy_on_push is false in floo.app.toml.
  Next step: Set deploy_on_push = true under [github] in floo.app.toml and push again, or run `floo redeploy --rebuild` to deploy the current default-branch commit.

Run it when a push produced no deploy in floo deploys list. It reads last_push from the GitHub connection; the outcomes and their next steps are listed in Why a push did not deploy. Exit code is 1 when needs_action is true (deploy_on_push_off or repo_linked_to_several_apps), and 0 otherwise.

managed-services

Report managed resources whose provision or teardown failed, across the app’s managed services and every preview’s managed resources:

floo doctor managed-services
floo doctor managed-services --app my-app
floo doctor managed-services --json

Each issue carries the resource, its environment (app for app-level managed services, the preview slug for preview resources), a stable reason code (provision_failed or deprovision_failed), and a remediation.

{
  "success": true,
  "data": {
    "app_id": "fb6e7446-2d02-4307-b05e-b00120620da5",
    "app_name": "payments",
    "checked_envs": 0,
    "degraded_detected": true,
    "issues": [
      {
        "resource_id": "7b0890a0-0f53-46e4-b4e7-04fda184cd66",
        "resource_kind": "managed_service",
        "type": "redis",
        "name": "default",
        "env": "app",
        "status": "failed",
        "reason": "provision_failed",
        "observed_at": null,
        "remediation": "Contact floo support to inspect the failed provision of default."
      }
    ]
  }
}

resource_kind is managed_service or preview_resource. Exit code is 0 only when issues is empty, so a successful request can still exit 1.

accounts

Compare the requested accounts-mode config with the gateway state serving it:

floo doctor accounts
floo doctor accounts --app my-app
floo doctor accounts --json

The command exits non-zero when its drift list is non-empty.

CLI

Config and runtime

Errors

API

push

managed-services

accounts

​push

​managed-services

​accounts

​Related

push

managed-services

accounts

Related