Hello, Is GoodData Cloud down? Or just me? From console:

Tiger backend threw an error: {detail: 'Server-side problem. Contact support.', status: 500, traceId: 'a1a91f375a11327b02d12dbc87615690'}

I cannot confirm whether there is a current, active outage — my knowledge sources only cover past incidents, all of which have been resolved. The "Unknown Error / We're not quite sure what went wrong" screen you're seeing (as shown in your screenshot) is a generic GoodData error that can have several causes: [Unknown Error cases] 1. Temporary platform issue – a short-lived service disruption that resolves on its own. 2. User/identity problem – a broken

authId

or OIDC mapping, especially if your user was created rather than invited. 3. Wrong environment – your user may not be provisioned in the specific org/domain you're trying to access (e.g., dev vs. prod). [Dev vs prod org] Steps to take right now 1. Check the GoodData status page at support.gooddata.com for any active incidents in your region (IAD1/us-east-1 or DUB1/eu-west-1). 2. Try basic troubleshooting: clear browser cache, try a private/incognito window, or a different browser. 3. Capture a Trace ID: open browser Dev Tools → Network tab → reproduce the error → copy the

traceId

from the failing request's response. 4. If production is impacted, open a Severity 1 support ticket at support.gooddata.com and include: ◦ Your organization URL ◦ Your login email ◦ When the issue started ◦ The

traceId

from step 3 ◦ Screenshots If you can share your organization URL and region, that would help narrow down whether this is a wider incident or something specific to your account. 👍 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.

@kapa.ai Organization URL: https://vision.lqdigital.com/ From console:

Tiger backend threw an error: {detail: 'Server-side problem. Contact support.', status: 500, traceId: 'a1a91f375a11327b02d12dbc87615690'}

index.D4i-SmVU.js:109 Uncaught (in promise) SC: Request failed with status code 500

at lQe (index.D4i-SmVU.js:109:352397)

at j1 (index.D4i-SmVU.js:109:351458)

at authApiCall (index.D4i-SmVU.js:114:51010)

Thank you for sharing those details. Here's what the error indicates and what to do next: The

status: 500

with

"Server-side problem. Contact support."

is a server-side error — it cannot be fixed on your end. The

traceId: a1a91f375a11327b02d12dbc87615690

is the key piece of information GoodData support needs to locate the relevant logs and investigate. [API Errors docs] This type of error has been seen in past cases and was resolved by GoodData engineering (e.g., an internal service stopping during a routine update, or a temporary platform issue). [Short outage fixed] Recommended next steps 1. Contact GoodData Support immediately at support.gooddata.com and open a ticket. If this is production-impacting, mark it Severity 1. Include: ◦ Organization URL:

vision.lqdigital.com

◦ `traceId`:

a1a91f375a11327b02d12dbc87615690

◦ When the issue started ◦ The full error message from your console ◦ Whether it affects all users or just specific ones 2. While waiting, you can also try invalidating the cache for your data source, as this has resolved 500 errors in some past cases. [Cache Management] 3. Check the status page at support.gooddata.com for any active incidents in your region. The

traceId

you've already captured is exactly what support needs to pinpoint the root cause quickly. 👍 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.

Hello Mark, there is no general issue so I think this is connected to your environment only. I see you raised a ticket with Support, they will take a look and reach out asap.