Workers¶
Workers defines host-level overrides for background job processing. Emakin uses different worker types for activities such as work-item processing, scheduled tasks, XML/full-text maintenance, email delivery, and assistant turns.
Open Operations → Workers. The Maintenance sub-tab in the same area contains the Redis cache flush action.
When to Use This Page¶
Use this page when default worker behavior is not suitable for your environment and you need to tune retry, timeout, or alert behavior for a specific worker type.
For job-state meaning and background processing context, see Background Jobs.
Warning: Incorrect worker settings can disrupt job processing performance and operational stability.
Saving Host Administration refreshes worker configuration while the application is running; restarting the agent is not required. Every optional override can be left empty to keep that worker type's built-in default.
Maintenance¶
Open Operations → Maintenance to manage the Redis cache connection. Flush Cache clears the shared cached configuration and runtime data so that nodes reload it on demand. When prompted, enter a cache-key pattern to remove only matching entries; * can match multiple keys. Leave the pattern empty, or enter only *, to clear the entire cache.
Warning: Flush Cache affects the whole application. Use it after configuration troubleshooting or a coordinated operational change, not as a routine refresh action.
Settings Reference¶
Worker¶
Selects which worker type the override applies to.
Priority¶
Controls job priority. Higher-priority jobs are processed before lower-priority jobs. Leave it empty to use the worker default. Available overrides are Low, Normal, High, VeryHigh, and Critical.
Timeout Period¶
Defines how long a job may keep running before Emakin treats it as failed. If left empty, the default worker value is used.
Delete After Period¶
Defines how long a job is retained after it is created before maintenance removes it. If left empty, the default worker value is used.
Maximum Retry Count¶
Defines how many times the worker retries a failed job before moving it to the maximum-retry state. If left empty, the default worker value is used.
Retry Period¶
Defines the interval between retries after a failure. If left empty, the default worker value is used.
Maximum Retry State¶
Defines the final state applied once the retry count is exhausted. Available overrides are Error, Completed, Aborted, and Waiting. If left empty, the default worker value is used.
Error State¶
Defines the state applied when the job fails. Available overrides are Error, Completed, and Aborted. If left empty, the default worker value is used.
Alert Errors?¶
Enables alert notifications for worker errors.
Alert Abort?¶
Enables alert notifications for aborted jobs.
Alert to System Admin?¶
Select Yes to send enabled worker alerts to the application address configured in System Administrator Email. Select No to send them to the domain administrators when the job has a domain context. Leave the value empty to use the worker default.