How to Assign ServiceNow Incidents in Round-Robin Order with Power Automate
Question details
The user wants to distribute ServiceNow incidents and tasks dynamically among active shift engineers using round-robin logic instead of assigning them to a single default user.

- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- Distributing workload evenly among multiple engineers assigned to a shift.
- Observed behavior
- The current Power Automate flow is restricted to assigning all ServiceNow incidents and tasks to one static default user.
Ensure you have the premium ServiceNow connector enabled in Power Automate and an established data source (such as a SharePoint list or an Excel table) to store and track your active shift engineers and their assignment index.
Build Round-Robin Assignment Logic in Power Automate
Construct a custom flow that tracks active engineers, remembers the last assigned person, and assigns the next incoming ServiceNow incident sequentially.
Because Power Automate does not have a built-in action for round-robin assignment, you must maintain a persistent variable or data record outside the flow (like in a SharePoint list or SQL table) to track whose turn is next across different flow runs.
Create a database or list (e.g., a SharePoint list) containing the system IDs or emails of all active engineers currently on shift.
Maintain a persistent tracking index (e.g., in a separate configuration list) that stores the row number or ID of the engineer who received the last assignment.
Add logic in your Power Automate flow to retrieve the tracking index, increment it by 1, and wrap it back to 0 if it exceeds the total count of active engineers.
Use the ServiceNow connector's 'Update Record' action to map the newly selected engineer's ID into the 'Assigned to' field of the incident.
Save the new index number back to your configuration list so the next triggered flow execution will accurately select the next person in line.

Consult the Power Platform Community
Post your specific configuration in the official Microsoft forums to get targeted troubleshooting for your ServiceNow connector and data structure.
Looking for a Lightweight Microsoft Office Alternative?
While advanced automated workflows require Microsoft Power Automate, you can easily handle your daily documentation, spreadsheets, and shift tracking with WPS Office. It provides a familiar, lightweight, and completely free alternative to expensive desktop Office applications.
- 1. Download and install: Visit the official WPS website to download the free WPS Office suite for your operating system.
- 2. Track shift rosters: Open WPS Spreadsheet to easily manage, organize, and track your engineering shift schedules.
- 3. Save with seamless compatibility: Save your engineer rosters in .xlsx format to ensure full compatibility with Microsoft Office users and external data connectors.

Frequently Asked Questions
What is round-robin assignment?
Round-robin assignment is a distribution method where tasks or incidents are assigned sequentially to each person in a group. Once everyone has received a task, the cycle starts over from the first person, ensuring an equal workload distribution.
Does Power Automate have a built-in round-robin action?
No, Power Automate does not include a native round-robin action. You must custom-build the logic using variables to track indices and an external data source (like a SharePoint list) to persist the last assigned user between flow runs.
Which Power Automate connector updates ServiceNow tickets?
You need the premium ServiceNow connector. Specifically, you use the 'Update Record' or 'Create Record' action and map the appropriate user ID to the 'Assigned to' field.
How do I prevent assignment errors when multiple incidents are created simultaneously?
Concurrency can cause race conditions in Power Automate where the index isn't updated fast enough. To prevent this, you can limit the trigger's concurrency control to '1' in the trigger settings, forcing the flow to process incidents sequentially.




