RunIDs generated out of numerical sequence - Automic Automation
Article ID: 445737
Updated On:
Products
Issue/Introduction
In Automic Automation, activities may be assigned RunIDs that appear to be out of numerical order relative to their start times. This behavior occurs when multiple Worker Processes (WPs) are active.
Environment
- Automic Automation Engine (All Versions)
Cause
This behavior is Working as Designed. Each Worker Process (WP) is allocated a unique pool of 1,000 RunIDs at a time from the database. Each WP assigns RunIDs from its reserved pool sequentially. Because different WPs process tasks at different speeds, a task started by WP A might receive a higher RunID than a task started slightly later by WP B if WP B's pool is numerically lower.
Resolution
No action is required as this is the standard architecture of the Automation Engine.
Sequence turnover occurs when the RunID ceiling (2^31) is reached, at which point IDs roll over (down) to 1,000,000.
Feedback
