Jobs in queues can fail—that's a reality! The good thing about jobs is that you can retry them because they have their own state.
In Flare, we've already been tracking failed jobs for quite some time; we can show you the job's initial state and where it went wrong.
We've added a new feature when you're using Laravel Horizon as a queue. Laravel Horizon provides a visual dashboard showing you all sorts of info about the queue, its failed jobs, and the ability to retry failed jobs. From now on, you can link your Flare project with the Laravel Horizon dashboard.
Every error triggered by a job in Laravel Horizon now links you to the failed job in the horizon dashboard. Allowing you to see even more info about the failed job and retry it:
You can read more about configuring this feature in our docs.
Continue reading
Why we removed AI solutions from Flare
AI generated solutions are dead, long live AI generated solutions! We removed the old one-shot fixes from a model that could only see the stack trace. It simply couldn't compete with modern agentic AI. In their place, Flare works with the agentic AI tools you already use: an MCP server that handles real triage, a CLI with an agent skill, quick Copy for AI prompts in the UI and docs served as markdown. Hosted agents are in the works too.
Alex
Flare now uses OAuth for MCP, the CLI, and API
Connect MCP clients like Claude and Cursor to Flare by logging in from your browser, no more copying API tokens. Every connection gets its own permissions, so you can give your AI read-only access to a single project. The CLI signs in the same way, and new personal access tokens with scopes and expiry cover scripts and CI.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
