lampard08
(Chelsea Blue)
March 14, 2026, 11:38pm
1
I am using Web Service SaaS connector for one of the ServiceNow resource end points.
the aggregation runs for about 6k records than hits the rate limit. Here is teh error in debug mode from SaaS logs :
“HttpClientWrapper.ts Rate limit caught… Retrying after 30 seconds.”
but i do not see the connector retrying again pr waiting instead I see it errors out and exits the aggregation.
I tried to increase the wait time by adding :
“retryWaitTime”: 60000
but I do not think it is being considered.
Any thoughts?
see the “for ServiceNow” section
lampard08
(Chelsea Blue)
March 15, 2026, 12:05pm
3
The paging works fine. I am looking for retry wait mechanism.
iamnithesh
(Nithesh Rao)
March 15, 2026, 12:59pm
4
This looks like due to some setting on ServiceNow side. Check this link, it might help you
lampard08
(Chelsea Blue)
March 22, 2026, 6:01pm
5
I understand the rate limit from servicenow but I am more interested why retry wait time is not working. Curious if I am not using it right.
BBR1
(Bharani Reddy)
March 22, 2026, 6:23pm
6
Have you verified whether the retryWaitTime you configured is actually being picked up during aggregation? Where have you configured this (retryWaitTime )
lampard08
(Chelsea Blue)
March 22, 2026, 11:31pm
7
I verified and it is not being picked. I have this in source’s connectorAttributes
BBR1
(Bharani Reddy)
March 23, 2026, 10:17am
8
Then it’s likely that this parameter is not supported for aggregation/pagination in the connector.
As a workaround, try avoiding the rate limit by filters (incremental aggregation using sys_updated_on) or controlling request volume, since retry handling is not reliable in this flow.
add this in your aggregation end post
https://instance.service-now.com/api/now/table/user?sysparm_query=sys_updated_on >=javascript:gs.daysAgoStart(1) this fetches records updated in past 1 day..
reference doc : Operation-Specific Configuration Parameters