Hi team, we're running into an issue in PROD. Every time the page is refreshed, fetching the filter values fails with an "Incorrect credentials" error. Please help check

"Incorrect credentials" on Filter Value Fetch Looking at your screenshot, the browser console shows: •

POST .../api/v1/actions/workspaces/.../execution/collectLabelElements

→ 400 (Bad Request) • Error detail:

"Incorrect credentials"

,

reason: "Incorrect credentials"

• `traceId`:

b3967e8f2d4f4822f6ed558cc8099f11

and

7ad2d892012aab65cdf251ae3ce3bda5

This is an authentication/credentials issue, not a data or filter definition problem. The API calls are being made but the credentials being sent are invalid or not being injected correctly. Likely Causes 1. JWT/token not being injected before API calls fire — A race condition where the auth provider hasn't finished initializing before the filter element loader fires its requests. This is consistent with a similar case in the community where "every single API request is sent without cookies AND without an Authorization header" due to the

TigerJwtAuthProvider

not injecting the

Authorization: Bearer <jwt>

header in time. [JWT auth issue] 2. Expired or invalid credentials/cookies — If you're using OIDC/cookie-based auth, cookies may have become invalid, causing the backend to reject requests with a 400 instead of a 401. [OIDC cookies] 3. SDK version mismatch — Mismatched GoodData SDK package versions can cause different initialization sequences, leading to auth headers not being applied correctly. [SDK mismatch] Immediate Steps 1. Provide the

traceId

to GoodData Support — The internal logs keyed to these trace IDs will reveal the exact cause: ◦

b3967e8f2d4f4822f6ed558cc8099f11

◦

7ad2d892012aab65cdf251ae3ce3bda5

1. Check your auth provider initialization — Ensure your

TigerJwtAuthProvider

(or equivalent) fully completes

setContext()

before any dashboard/filter components mount and fire requests. 2. Verify token validity — Confirm the JWT or API token being used is still valid and not expired at the time of the page refresh. 3. Check SDK package versions — Make sure all

@gooddata/sdk-*

packages are on the same version to avoid initialization sequence mismatches. 4. Capture a HAR file — Record a HAR file reproducing the issue and share it with GoodData Support along with the trace IDs, your workspace ID, and the time of failure. [API errors] Since this is a PROD issue, I'd recommend opening a support ticket at support.gooddata.com immediately with the trace IDs above for fastest resolution. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Hi Phuc, thank you for this. We are facing an issue in our platform. Our engineers are aware of this and they are working in the fix. Please follow our announcement to follow the updates. Our apologies for this inconvenience.