Hi team, how can I know the exact error for this failure,

{
  "title": "Bad Request",
  "status": 400,
  "detail": "An error has occurred while calculating the result",
  "resultId": "cfa962dad0163cd5a8e5e9b16a23cd338d111196",
  "reason": "General error",
  "traceId": "c127f8812f3328ebaa0917590876eeed"
}

You can’t decode the exact root cause just from that JSON alone; the real detail is only visible in GoodData’s internal logs, which are keyed by the

traceId

. [[API errors](https://www.gooddata.com/docs/cloud/api-and-sdk/api/errors/); [Error payload](https://www.gooddata.com/docs/cloud/api-and-sdk/api/errors/#error-response-payload)] To get the exact error: 1. Capture the traceId (you already have

c127f8812f3328ebaa0917590876eeed

). 2. Open a support channel: - If you use GoodData Support, create a ticket and include: - the

traceId

- time of the failure - workspace ID - which visualization/API call you were executing. - If you’re using Community Slack, you can share the traceId there and staff can look it up in internal logs, as in similar cases. [[Slack traceId usage](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1709118204208749); [Another traceId example](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1741636752816999)] End‑users don’t have direct access to those internal logs, so contacting support with the traceId is the only way to see the precise SQL / permission / data‑model error behind a generic

"reason": "General error"

.

Hi Ayush, from our logs we can see a “DATA ERROR”. The result cache shows DATA_ERROR and turns that into the

400 Bad Request

with “An error has occurred while calculating the result”. The underlying cause is likely an issue in the report. I would suggest to review the report directly in the UI

@sameer mehra can you check

Hey the visualisation works fine on the gooddata. Attaching ss FYR . But when we are trying to show visualisation on our CRM , we are facing this errror ""detail": "An error has occurred while calculating the result",", We are using visual component approach btw. I tried creating a new visualisation, but the error remains the same. Have shared below one of the visualisations that is not working. https://gokenko.cloud.gooddata.com/analyze/#/5dc926cc134043c18c7f79008cc8fd65/6bc353db-88ec-4733-b26c-505b7557b3d3/edit

Hi Sameer, the visualisation itself is OK (it runs fine in GoodData), so the error in the CRM is most likely caused by something that’s different in the embedded context rather than by the chart definition. Please try to open your browser dev tools in the CRM, reproduce the error, and copy the

traceId

from the failing

/executionResults

(or similar) request and provide us with the related TraceID and we will review our logs for you.

Hey @Michael Ullock sharing some visualisations that are working for us on GD platform but not on FE along with the visualisation link and their trace id's . Visualisation 1 - https://gokenko.cloud.gooddata.com/analyze/#/5dc926cc134043c18c7f79008cc8fd65/a2442a84-de60-4bfc-b37d-4ba4d1596e26/edit Trace ID 1 - 085ac62c8c7fd4b99b427846247a2c8b Visualisation 2 - https://gokenko.cloud.gooddata.com/analyze/#/5dc926cc134043c18c7f79008cc8fd65/9e73faa4-a9fa-4b8d-8690-a3d2fba3ed13/edit Trace ID 2- 0a7266576e53faba33fc8d8d413ac68a Visualisation --3 -https://gokenko.cloud.gooddata.com/analyze/#/5dc926cc134043c18c7f79008cc8fd65/58614480-9d56-4728-b814-ac0d21bee3c4/edit Traced ID -3 - 07598096c66243b4e72f5a7a4840944a

Thanks for sharing the visualization links and traceIds — that helps us locate the server-side error in our logs. To understand why this only fails in the embedded CRM context (and works in the GoodData UI), we’ll also need a bit more client-side detail. Could you please capture a HAR file while reproducing the issue in your CRM (DevTools → Network → Preserve log → reproduce → “Save all as HAR with content”), or alternatively share the failing

/executionResults

request payload and response from the browser network tab? This will let us compare the embedded execution with the one running in GoodData and pinpoint the difference.