Jobs & queues
Flare can collect information about the jobs being executed in your application. This includes:
- The job name
- The job class
- The job queue
- The job connection
- The job UUID
- The job tags
- The job properties
- And so much more...
Open an error occurrence's job entry in the timeline to inspect the available context. The Laravel SDK listens to job lifecycle events and reads queue metadata and the serialized job payload to collect this information. Captured properties are debugging context, not a complete snapshot you can replay. A job exception can come from an unsuccessful attempt before the job has finally failed.
This functionality is enabled by default, but you can disable it by ignoring the Jobs collect in config.php:
use Spatie\FlareClient\Enums\CollectType;
'collects' => FlareConfig::defaultCollects(
ignore: [CollectType::Jobs],
),
You can configure the maximum number of jobs tracked while collecting data in the case of an error as such:
'collects' => FlareConfig::defaultCollects(
extra: [
CollectType::Jobs->value => [
'max_items_with_errors' => 10,
],
]
),
When a job is executed, its further chain of jobs will be collected to provide even more insight into the job and its chain. It is possible to define the maximum depth of such a chain as such:
'collects' => FlareConfig::defaultCollects(
extra: [
CollectType::Jobs->value => [
'max_chained_job_reporting_depth' => 5,
],
]
),
To disable the inspection of job chains, you can set the depth to 0:
'collects' => FlareConfig::defaultCollects(
extra: [
CollectType::Jobs->value => [
'max_chained_job_reporting_depth' => 0,
],
]
),
When you want to ignore specific job classes, you can do so by adding them to the ignored_classes array. Entries can be exact class names or wildcard patterns using *:
'collects' => FlareConfig::defaultCollects(
extra: [
CollectType::Jobs->value => [
'ignored_classes' => [
App\Jobs\SomeJob::class,
'App\\Jobs\\Internal\\*',
],
],
]
),
Patterns are checked against both the job's name and class.
Laravel Horizon
Laravel Horizon manages workers for Laravel's Redis queues. You don't need Horizon to collect job context in Flare. If you use it, you can connect your Flare project to its dashboard to inspect and retry failed jobs there.
Configuration
Within your project settings, open the Laravel page:

Enter the full URL to your Laravel Horizon dashboard, for example https://your-app-domain.com/horizon, without a trailing slash, and click Save settings.
Usage
When a captured job entry is identified as a Horizon job and has a UUID, the occurrence timeline can show Open this job in Laravel Horizon. This shortcut uses your project's configured dashboard URL:

Access and retention
If the link is missing, check your project's Horizon URL and that a Horizon worker processed the job. You still need permission to access your application's Horizon dashboard; the link doesn't bypass its authorization rules.
Please note that by default, Laravel Horizon will keep the failed job information for seven days; failed jobs older than seven days will no longer be available in Horizon. You can adjust this setting in your horizon.php configuration by updating the trim option:
'trim' => [
'recent' => 60,
'pending' => 60,
'completed' => 60,
'recent_failed' => 43200, // 30 days
'failed' => 43200, // 30 days
'monitored' => 10080,
],
On this page