Short answer
Ask the assistant. Fieldproxy's built-in why_did_this_automation_fail workflow lets ChatGPT, Claude or Copilot list failed runs, explain the cause, and then retry or dismiss them, simulate a change, or restore an earlier version of the rule. Retries and restores are proposals you confirm.
What to ask
- "Why did last night's invoice automation fail?"
- "Retry the three failed runs."
- "Would this change have worked?"
- "Go back to yesterday's version of the rule."
How it works
The workflow uses list_failed_runs and list_automation_runs, then retry_automation_run or dismiss_failed_run, simulate_automation, and list_automation_versions with restore_automation_version.
Anything that changes data or sends a message is shown to you first and happens only after you confirm; writes can be undone, and every call is logged.
Fieldproxy facts on this page come from the Fieldproxy MCP reference. Competitor details are from each vendor's own documentation as of September 27, 2026; see the comparison table and sources.