SG‑Meraki Integration – Import Sets Stuck in Loading

[Aman Trivedi1]

Hi Team,

We are facing an issue with the Service Graph Connector for Meraki (SG‑Meraki). 

🔍 Issue Summary

• Import sets (x_caci_sg_meraki_merakidevices) are frequently getting stuck in Loading state
• Some import sets are marked Processed but contain 0 records
• Scheduled jobs occasionally get stuck or lead to long-running executions
  

From system logs and import logs, we observed:

• HTTP 503 (Service Unavailable) – occurring in initial API calls
• HTTP 429 (Rate limit exceeded)
• Parsing errors:
  • Payload for JSON Parser: undefined
  • JSON must be an object or array
• Occasional:
  • Cannot read property 'id' from undefined

Has anyone else faced similar issues with SG‑Meraki integration??

[rush_man]

Import stuck at 'Loading' state. The scheduled import kept attempting to import and created 4 import attempts. That generated loads of GET requests, slowing down our instance. 

Eventually the recent attempt the next day morning has a 'Completed' state but nothing brought in. 

ServiceNow shared this KB article to follow "SG-Meraki Devices" job building large objects leading to memory exhaustion - Support and Troublesho...
But it does not has resolution but more like kill the hung jobs. 

We still investigating 

[Aman Trivedi1]

Hi @rush_man ,

I am facing the exact same issue on my side as well.

• The SG-Meraki Devices scheduled job starts successfully
• During execution, the import set gets stuck in Loading state
• The job keeps retrying and creates multiple import sets
• We are also seeing Out of Memory errors in the logs
• The number of active SG-Meraki transactions is very high

It seems this could be a broader issue affecting multiple implementations.

Since when did you start noticing this issue?

[Christoffer Vir]

My customer has the same issue as well. 

• The SG-Meraki Devices scheduled job starts successfully
• Import stuck in Loading state
• The job keeps retrying and creates multiple import sets
• ServiceNow has flagged that the instance runs out of memory because of the import.

It keeps fetching the same record over and over again. 
It also gets rate limited by the API (which doesn't practivally matter as it's looping).

That is also the only error message i'm getting in the logs  "code: 429 - API rate limit exceeded"

The loop causes the ServiceNow instance to run out of memory. We have been forced to disable the import.

[Aman Trivedi1]

..

[Aman Trivedi1]

..