Why do my queued jobs throw CurrentTenantCouldNotBeDetermined when dispatched from public routes? #29
Answered
by
Kevinchamplin
Kevinchamplin
asked this question in
Q&A
Why do my queued jobs throw CurrentTenantCouldNotBeDetermined when dispatched from public routes?
#29
-
|
Why do my queued jobs throw CurrentTenantCouldNotBeDetermined when dispatched from public routes? |
Beta Was this translation helpful? Give feedback.
Answered by
Kevinchamplin
Jun 13, 2026
Replies: 1 comment
-
|
spatie/laravel-multitenancy defaults queues_are_tenant_aware_by_default => true, so every job expects a current tenant at run time. Jobs dispatched from a landlord/public context (e.g. a signup provisioning pipeline) have none and die. For landlord-heavy apps set it to false in config/multitenancy.php and opt in per-job via the TenantAware interface only where you need tenant context. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Kevinchamplin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
spatie/laravel-multitenancy defaults queues_are_tenant_aware_by_default => true, so every job expects a current tenant at run time. Jobs dispatched from a landlord/public context (e.g. a signup provisioning pipeline) have none and die. For landlord-heavy apps set it to false in config/multitenancy.php and opt in per-job via the TenantAware interface only where you need tenant context.