@adamian, from my best understanding, “request_milliseconds” is an integer which has a max limit of "32767" (i.e., 2^15 -1), and if it goes beyond that it will overflow which is why you see a negative value there.
I believe the data type used for “request_milliseconds” should be re-considered by SailPoint product team for edge-cases like these!
Hi @gauravsajwan1, I think there is more to it than this. In the example posted the value is less than -32768. In the logs there are also values bigger than 32k, for example 876107, 2007545.
Also, the negative value that you see on the ccg.log is not the “exact” milliseconds value which was attempted to be assigned to the request_milliseconds parameter.
What does a negative request_milliseconds mean in the ccg.log?
This is related to an NTP issue, where the time received from another source (e.g. cloud) is out of sync with the current local time, as NTP isn’t properly configured (aka time sync is not working).
As per the logs in your screenshot, VA is communicating with ServiceNow for a web service API call which is initiated by SailPoint ISC.
“request_milliseconds” either could belong to SailPoint ISC or VA (if it’s a NTP issue). Did you check with SailPoint support on this? Also if you believe it’s NTP, did you verify your local NTP config file?
Also, how long does it take to successfully complete a test connection for your ServiceNow source?