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
Create richer issues from your errors
When Flare creates an issue on GitHub, GitLab or Linear, you can now pick the assignee and labels right away.
Ruben
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
