Legacy deployment task execution service being removed
The background worker logic responsible for tracking and triggering tasks waiting for deployment is being removed, as the queue responsibility shifts to a dedicated Redis worker.
The internal application service responsible for tracking and executing tasks waiting for deployment is being removed. This responsibility is now delegated entirely to a dedicated Redis worker.
Centralizing this queue management simplifies the application architecture and removes redundant polling mechanics from the main web application layer. The legacy system previously queried the database for stalled tasks and explicitly fed them back into the queue. By shifting this to the Redis worker, background deployment workflows become leaner and more resilient.
This cleanup takes place primarily within the v3 worker and deployment background services, dropping over a hundred lines of legacy execution logic.