We are experiencing the same issue! We have a worldwide product deployed in different locations and we notice that only the US datacenter is affected by this issue at the moment!
Any feedback from Microsoft? This is a blocker issue!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We're having an issue where the nextLink with the skipToken is coming back and it is being used as-is for the next call. We get a random skipToken is invalid.
I've tested the url with Graph Explorer and it works. If I add extra characters at the end then I can induce the skipToken error. We haven't found anything on our servers that are adding characters.
Does the Graph API have an occasional issue with skipToken as of Jun 15, 2021?
Could it be something in transit that I haven't thought of?
We are experiencing the same issue! We have a worldwide product deployed in different locations and we notice that only the US datacenter is affected by this issue at the moment!
Any feedback from Microsoft? This is a blocker issue!