ATF errors: FAILURE: Failed to submit the record producer or Failed to submit catalog item after cloning and upgradation to Newyork
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-23-2019 10:59 PM
We have cloned instance from prod to dev.
After cloning when we are testing ATF, ATF tests are not working properly and it is showing the error message like: FAILURE: Failed to submit the record producer or Failed to submit catalog item.
ATF tests are working fine before cloning. After cloning we have imported xml related ATF update sets, while testing we are getting the ATF related errors.
We have followed some community posts and KB articles(https://hi.service-now.com/kb_view.do?sysparm_article=KB0751730).
later we have also upgraded our instance from London version to Newyork version,
and still we are getting the same ATF issues: FAILURE: Failed to submit the record producer or Failed to submit the catalog item. the ATF tests are working fine before cloning. After cloning and upgradation the ATF tests are not working properly.
if anyone is facing the similar kind of issue after cloning or upgradation ,Please help me out this atf issue.
- Labels:
-
Automated Test Framework
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2019 12:12 AM
Hi,
I have faced similar issue.
Probable causes: you are using custom portal and submitting record producer from that
Workaround: you can use out of the box portal to open the record producer and then set values and submit or you can use custom UI steps to click the Submit button
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-30-2019 02:38 AM
Hi Ankur Bawiskar,
We are using OOB Portal. It is not custom portal.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2020 06:16 AM
Try to set up Timeout for areound 10 s.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2022 08:47 AM
This solution worked for me. Thanks!
update: 10/05/2022