Skip to content

ActiveJob Extension not working for Solid Queue #352

@drale2k

Description

@drale2k

I just switched from GoodJob to SolidQueue and noticed that the ActiveJob extension responsible for setting a current_tenant seems not to work for Solid Queue

This is the meta data of one of my jobs and the current_tenant key is missing. This is the case for all of my bg jobs now but it worked for GoodJob.

  {
  "id": 137107,
  "queue_name": "fast",
  "class_name": "Alert::ScanJob",
  "arguments": {
    "job_class": "Alert::ScanJob",
    "job_id": "36babf66-8677-4a78-b672-5039db59fdef",
    "provider_job_id": null,
    "queue_name": "fast",
    "priority": null,
    "arguments": [
      {
        "_aj_globalid": "gid://nebula/Alert/72"
      }
    ],
    "executions": 0,
    "exception_executions": {},
    "locale": "en",
    "timezone": "UTC",
    "enqueued_at": "2025-06-17T14:30:01.948724784Z",
    "scheduled_at": "2025-06-17T14:30:01.948676735Z"
  },
  "priority": 0,
  "active_job_id": "36babf66-8677-4a78-b672-5039db59fdef",
  "scheduled_at": "2025-06-17T14:30:01.948Z",
  "finished_at": "2025-06-17T14:30:04.123Z",
  "concurrency_key": null,
  "created_at": "2025-06-17T14:30:01.948Z",
  "updated_at": "2025-06-17T14:30:04.123Z"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions