Action worker behavior
Action workers process actions asynchronously in the background. Depending on the action definition, this can include script automation and API calls. Action worker behavior is influenced by the action definition, the action type, the execution mode, the amount of data being processed, and the overall system load, including concurrent activity.
How an action worker behaves starts with the action definition, which specifies the instructions that the action follows. Then:
-
The action is triggered through the user interface, by a trigger, or by an API call.
-
The action is added to the actions queue. If you are a superuser or have the necessary permissions granted to you through user group policies, you can see what is in the queue by clicking Manage
> Stats and then clicking the Current activity tab. -
The action worker picks up the action and executes it.
-
The execution results are recorded in the action audit logs.
Content Hub supports adaptive scaling based on queue load and activity, which is the automatic management of capacity and performance. During normal operation, action processing can vary over time:
-
Processing speeds can increase or decrease.
-
Queued tasks can take longer to start during a heavier processing workload.
-
Work can appear to complete in batches.
These behaviors are expected when demand changes. If tasks take longer than expected to complete or processing appears delayed, review the action logs to confirm whether work is queued, in progress, or completed.
Dynamic scaling is system-managed by Content Hub and cannot be configured through the user interface.
See Best practices for developers for additional recommendations on script types and triggers. Content Hub information architects and those in technical roles can find more detailed information about script guidance and how to optimize performance in the Accelerate Cookbook for Content Hub, a collection of recipes that provides information to help you successfully set up, configure, and implement Content Hub.