What this agent helps you do
A Cloudflare and Sentry incident fix agent helps reliability teams investigate incidents across the edge and the application. Cloudflare contributes traffic, cache, worker, firewall, and performance signals, while Sentry contributes exceptions, releases, traces, stack traces, and affected user evidence.
When to use this workflow
Use it during active incidents, post-incident reviews, route-specific outages, worker regressions, or release problems where platform symptoms and app errors need to be correlated.
How Cloudflare and Sentry give the agent context
Connect both plugins and provide a narrow incident window, affected route, deployment, or customer report. Cloudflare should establish request behavior and edge changes; Sentry should identify application failures and user impact. Require approval before any firewall, worker, rollback, or configuration change.
Example starter prompt
Correlate Cloudflare traffic, cache, worker, and 5xx signals with Sentry issues for this incident window. Prepare an incident brief with a timeline, likely causes, customer impact, safe remediation options, and validation checks. Do not make operational changes without approval.Suggested workflow steps
Start with the incident window and affected route. Have the agent compare Cloudflare anomalies with Sentry issue volume, releases, and stack traces, then group findings by likely cause and confidence. The agent should identify whether the first visible symptom appears at the edge, in the app, or in both systems.
Expected handoff
Ask for a timeline, source-by-source evidence, blast radius, likely cause, recommended fixes, rollback considerations, validation checks, and explicit approval-required actions.