tenant-safe-background-jobs

Prevent cross-tenant data leakage by enforcing tenant-scoped background jobs that require a tenant_id in every payload and reconstruct per-tenant context before processing. This avoids shared global state across concurrent workers.

Tenant context propagation in multi-tenant workers is the process of reconstructing tenant-specific context from the job payload. Workers re-fetch the tenant from the database, validate status and entitlements, and build isolated per-tenant contexts for downstream calls.

Handle global platform jobs by fanning them out into individual per-tenant jobs. This ensures no cross-tenant contamination occurs, as each generated job carries a specific tenant_id and operates within its own safe, isolated context.

Yes, you need to validate tenant entitlements during async job execution to ensure safe worker context. Workers re-fetch the tenant from the database, check tenant status, and validate entitlements before building per-tenant context for downstream calls.

Yes, you can implement per-tenant retries and DLQ behavior for tenant-scoped background jobs. This isolates failed jobs to the specific tenant context, preventing retry storms or DLQ contamination from affecting other tenants in the multi-tenant SaaS platform.