Skip to content

Background Jobs

Emakin performs many heavy operations in the background so that user actions can complete quickly while processing continues asynchronously. Domain administrators use the background job pages to monitor queued work, investigate failures, and re-queue or abort jobs when operational intervention is required.

How Background Jobs Behave

When a user initiates a process, Emakin records the workflow state in the database first and then creates the required background jobs. Service agents pull those jobs from the queue and process them without further user interaction.

If a job fails during processing, the transaction is rolled back and the error is reported to administrators. After the underlying issue is resolved, the job can be re-queued from the job manager. Some job types recover automatically and return to the queue after a delay.

Background job architecture showing queued work being processed by service agents.

Service agents can use multiple threads and can be deployed to multiple hardware instances for parallel execution. Jobs are processed according to priority. The documented baseline is that a single service agent can complete roughly 600 jobs per minute for basic workflow operations, although actual throughput depends on the job type and hardware.

Job State Lifecycle

Every job starts in the Waiting state.

When a service agent picks the job from the queue, it locks the job and changes the state to Processing.

If the job completes successfully, the state changes to Completed.

If a job fails, the state changes to Error and the system notifies administrators. Some errors are retried automatically. For example, email sending failures can be rescheduled and returned to Waiting so the system can try again later. If the retry limit is exceeded, the state changes to Error or Aborted, depending on the job configuration.

Jobs in Aborted or Completed state are automatically deleted after their Delete After date passes.

Background job state transition diagram.

Typical Workflow

  1. Open Background Jobs Manager to review waiting, processing, error, completed, or aborted jobs.
  2. Filter by job type, time period, instance number, or log content.
  3. Open the problem job and inspect its details, log, data, and graph tabs.
  4. Re-queue the job or abort it after the underlying issue has been understood.
  5. Use the statistics pages when you need broader trend or capacity information.