Asynchronous import sets stuck in Loading state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 12:38 AM
Hello Assembled Wisdom of the ServiceNow world!
I've read many posts and support articles about synchronous import sets getting stuck in Loading state. However, I have not seen any in regards to asynchronous ones.
I am working with a client that is using Insert Multiple functionality of Import Set API to import relatively large amounts of data. Each import set has between 8 and 10 thousand of records, which takes a while to load. However, once the import sets are loaded, they are stuck in Loading state. I can manually change the state to Loaded and then, again manually, run the transform but that is obviously not a solution. There are no issues with import sets in the same table that are smaller in size.
Does anyone have any hints or has encountered this issue in the past? Could the reason be long loading time of the import set? ServiceNow documentation talks about keeping import sets under 100k records and we are way below that ... They are on Utah, if that makes any difference to anyone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 01:39 AM
In case this helps someone, we figured out what the problem was.
The integrating party is sending an extremely large payload, which ServiceNow then splits into different import sets automatically. However, the payload is so big, system can't receive it and the partner gets an internal server error (500). That causes ServiceNow to never actually finish "loading", leaving the import sets in the Loading state.
We will now have them send data in chunks which should sort the issue out.
