ATF error - "Unable to find the rollback context id for recording the server step execution" when trying to create a user

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2020 09:14 AM
I am currently working on automated test (ATF) for a record producer.
In order to follow the recommended practices, I try to create a new user instead of impersonating an existing one in my ATF. When executing the test, I get the following error message: Unable to find the rollback context id for recording the server step execution
Does anyone an idea of what might causing it?
Thanks in advance!
- Labels:
-
Automated Test Framework
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2020 09:45 AM
Hi,
check below links
https://hi.service-now.com/kb_view.do?sysparm_article=KB0727656
Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2022 01:17 AM
Hi Alexandre,
I started to face the exact same issue after upgrading to Tokyo.
Tried the solution mentioned in https://hi.service-now.com/kb_view.do?sysparm_article=KB0727656 but that was not helpful .
Could you please share how this was resolved. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2023 06:55 AM
Hi, I am having the same issue. Did anyone know how to resolve this? When running ATF I am getting this error:
Unable to find the rollback context id for recording the server step execution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-24-2023 07:47 AM
Hello,
In my case the issue was due to clone and the sys_number_counter was preserved for some reason.
If there are existing records in the table "sys_rollback_context" and the counter is at a number that is trying to insert records where they already exist it was logging this error.
Setting the sys_number_counter for sys_rollback_context to the highest number in the table resolved the issue.