Last updated 8 June 2026
Projects / Background Worker Infrastructure

Background Worker Infrastructure

Target / 30th June 2026 +32 days

Introduce a dedicated worker service to run long-running jobs more reliably and cost-effectively than serverless.

Open in Linear

Move long-running and resource-intensive background jobs out of Vercel/Inngest into a dedicated worker application to reduce compute costs, avoid serverless time limits, and improve reliability.

Focus is on supporting workloads like reporting and batch processing in a more scalable and predictable way.

Outcomes:

  • Reduced spend on serverless/background job execution
  • No timeouts on long-running jobs
  • More consistent execution of critical background tasks

Status

In Progress

Target

30th June 2026 +32 days

Lead

Oliver Soar

Teams

Platform, Releaf UK

Project updates

Recent status notes posted directly on this project in Linear.

1 shown

Oliver Soar

8 May 2026

On Track

Open in Linear

We have started moving cron jobs to Trigger.dev due to the flakiness of Inngest. Easier implementation and avoids us having to manage infra of the runner, queue and other components if we were to run our own with Google Cloud/Upstash for example.

Issues

Grouped by current Linear workflow status.

3 total

In Progress

1

  • RLF-6514 - Migrate rest of functions to Trigger.dev
    In Progress

Done

2

  • RLF-6379 - Move further reminder functions over to Trigger.dev
    Done
  • RLF-6377 - Move prescription reminders to Trigger.dev
    Done