Emakin performs most of the its heavy operations in on the background to achieve scalable and high performance outputs. These background operations are executed by emakin Emakin’s service agent without any user interaction.
When a new process is started initiated by the a user, workflow state is recorded in the database without any further processing, and creates a couple of background jobs. Service agents pull retrieve the jobs from the queue and try to process in on the background. If an error occurs while processing the a job, transaction state is rollbacked and error state is reported to the system administrators. When an administrator resolves the an issue, job is re-queued in the system, from the job manager, to the process again. Some of the errors are automatically recovered by the system and queued again with time delay.
...
...
Service agents use multiple threads, and can also be deployed to any number of hardware instances to perform parallel execution. Jobs are executed in order of priority, and a single service agent can complete 600 jobs per minute for the basic workflow operations. This number is highly dependent on the job definition and hardware specifications.
...
Each job contains a log about detailed information of what is performed in the background. Each log line has an in log level like Debug, Information, Warning, Error.
...
Job Types
Workflow Jobs
...