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
Version 2 of our JavaScript client libraries
We shipped v2 of @flareapp/js, @flareapp/react, @flareapp/vue, and @flareapp/vite. The framework packages now handle error boundaries, automatic context collection, and component prop capture out of the box. The core client talks to a new, faster ingestion endpoint, and the Vite plugin got retry logic and smarter sourcemap handling.
Sébastien
Flare ❤️ Livewire
Flare has deep Livewire visibility: components nested in traces with full hierarchy, per-phase timing (mount, hydrate, render, dehydrate), aggregated component views with bidirectional links, rich error context, and a lot more. Let us show you how Flare can assist in debugging your Livewire project.
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
