Managing Async queues and actions

You can manage the maximum number of actions and threads for a specific process to improve processing efficiency.

  • Action settings are defined in the Async queue.
    • Max Tenant Actions Count defines the maximum number of actions that can run across all products and queues for a specific tenant. Any action submitted after the maximum number of actions is running will wait in the queue until one of the running actions completes.

      Max Tenant Actions Count is a system-level setting that is managed by Infor Cloud Operations and determined during initial system deployment.

    • Max Active Actions defines maximum number of actions that can run concurrently for a specified queue. To update this setting, see Managing Async queues
  • Thread settings are controlled by Max Action Threads and Number Of Threads.
    • Max Action Threads defines the maximum value allowed for any Number Of Threads setting.

      The standard value for Max Action Threads is dynamically set to a default of one-half the value of Max Tenant Actions Count. This ensures that an action does not consume all available threads and allows for other active actions across products, such as Infor Financials and Supply Management.

      The Max Action Threads can be overridden in special cases by changing a configuration parameter. See Overriding the maximum active threads setting.

    • Number Of Threads defines the level of multi-threading or concurrent processing that can be performed by that action. See Using the Action Configuration utility

      If your Number of Threads is set to a value greater than the Max Active Actions on a queue, it means that when a multi-threaded action creates all the threads, some threads will be queued up to process after other threads complete.

      For example, if Number of Threads is set to 4 on the AssignTaxDeductions action, the work to be performed by that action is divided into four processes that run simultaneously if the queue has available active slots to process them. This allows the AssignTaxDeductions action to run in less time than if Number of Threads were set to 2.

  • The HCMGlobalHRActions queue is available as the HCM Global HR Default Queue for running single-threaded background actions instead of using the default queue.
  • Note: When the Action Configuration utility is not enabled, use HCM_RunGroups. See Configuring concurrent actions with HCM_RunGroups.