Summary
The existing per-workitem daily flow launch limit is being replaced with a per-workitem hourly limit for Work Automation.
Today, the workitem.workitemflow.launch.per.day limit controls how many times an individual workitem can launch its associated workitem flow within a day (reset at midnight UTC). Workitem flows are triggered by worktype rules, including on-create, on-attribute-change, and date-based triggers. When the daily limit is reached, flow launches are rejected with HTTP 429 and the error code:
service.limit.workitem.workitemflow.launch.per.day.limit.reached
The following changes are being introduced:
Deprecation of the daily limit
- workitem.workitemflow.launch.per.day will be marked as deprecated.
- New override requests for this limit will no longer be accepted.
- Enforcement of the daily limit will be removed after a - migration period.
Introduction of an hourly limit
- New limit key: workitem.workitemflow.launch.per.hour
- Scope: Per individual workitem
- Default: 20 launches per hour (configurable up to 50)
Effective Date
Monday, October 12, 2026
Details
Genesys has received multiple requests to increase the workitem.workitemflow.launch.per.day limit. Rather than continuing to increase the daily limit, Work Automation is moving to an hourly rate limit that better supports sustained workloads while continuing to protect the platform from short-duration traffic spikes.
Customer Impact
Customers using Work Automation will now be subject to an hourly launch limit instead of a daily limit.
Key changes include:
- The new workitem.workitemflow.launch.per.hour limit has a default value of 20 launches per hour.
- Customers that generate many workitem flow launches in a short period may reach the hourly limit sooner and should distribute launch activity more evenly throughout the hour.
- The daily limit (workitem.workitemflow.launch.per.day) will remain during the migration period but will eventually be removed.
- New override requests for the deprecated daily limit will no longer be accepted.
Customer Action Required
Customers should review any automation or business processes that generate large numbers of workitem flow launches and verify that launch activity remains within the new hourly limit. If launch activity is concentrated into short time windows, customers should consider distributing it more evenly across the hour.
Impacted Resources
No public API endpoints are directly affected.
This change impacts the rate limiting applied to workitem flow launches initiated internally by Work Automation. Customers may observe the following rate-limit changes:
- Deprecated: workitem.workitemflow.launch.per.day
- Error code: service.limit.workitem.workitemflow.launch.per.day.limit.reached
- New: workitem.workitemflow.launch.per.hour
- Error code: service.limit.workitem.workitemflow.launch.per.hour.limit.reached
Workitems are created using:
- POST /api/v2/taskmanagement/workitems
The new hourly limit applies to subsequent workitem flow launches triggered by worktype rules.
Issue References
WORKITEMS-8020
Contacts
@Caoimhe Rice @Saurav Kumar Mehta Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.