We are experiencing intermittent 401 errors related to “insufficient scope” when using the API, even though the service account key has all required permissions configured correctly.
These errors appear randomly and affect batch processing requests in particular. There have been no changes on our side (no key rotation, no permission updates, no config changes), which suggests the issue may not be client-related.
Given that there was an incident around April 10, it feels like not all servers or environments handling API requests have been fully updated or synchronized. The behavior is inconsistent, which further points to possible partial rollout or infrastructure desynchronization.
Could you please confirm:
-
whether there are still ongoing issues related to API authorization or batch processing,
-
and if partial deployment or cache inconsistencies across servers could be causing intermittent scope validation failures?