Home

Note on workers: Because the withdraw process involves a series of steps, several of which involve jobs that are enqueued at an external service, the browser will time out long before all steps are completed. To ensure delivering feedback to the user, the processing will be handed off to a worker and the browser will return immediately with where results will be written when complete; the user can come back once the process has finished and view the report.

Although each worker ideally has multiple threads, there is no guarantee of a job only being run once; eg, where there are 5 threads, an enqueued job will be run 5 times. To avoid this, each worker is configured with only 1 thread and 1 queue. At the moment, there is one worker per container. When the central service gets a request for a process that must go to a worker, a job is created and pushed to a given queue (chosen by the user).