Hi GoodData team, I'm having trouble saving change in one logical model, while in the other it works perfectly error message, whithout model name is here

"content=ldm status=500 error={\"timestamp\":\"2026-08-07T11:49:01.614+00:00\",\"path\":\"/api/v1/layout/workspaces/ MODEL-NAME/logicalModel\",\"status\":500,\"error\":\"Internal Server Error\",\"requestId\":\"1eb0c351-20225\"}"

Hi! The error you're seeing is a 500 Internal Server Error on the

PUT /api/v1/layout/workspaces/{workspaceId}/logicalModel

endpoint — this is a server-side error that cannot be fixed on your end. [API Errors docs] Here's what you should do: Immediate Steps 1. Contact GoodData Support at support.gooddata.com and provide: ◦ Your `requestId`:

1eb0c351-20225

◦ The affected workspace ID (the one where saving fails) ◦ The fact that the same operation works on another workspace — this is useful context for narrowing down the issue ◦ The timestamp:

2026-08-07T11:49:01.614+00:00

1. Retry the request — some 500 errors are temporary. A similar case in the community resolved itself after a few minutes of retrying. [LDM layout timeout] 2. Check the request headers and body — a past similar case turned out to be related to incorrect headers or request body format when uploading a layout. [Layout upload 500] 3. Check for LDM data type mismatches — if you recently made changes to the model (e.g., column types, references between datasets), validation errors can cause save failures. [LDM save error] Key Note Since the same LDM operation works on another workspace, the issue is likely specific to the configuration or state of the failing workspace, not your LDM payload itself. GoodData support can use your

requestId

to look up the exact root cause in their internal logs. [API Errors docs] 👍 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 Sanja, we are looking into this, can you please let us know when you saw the first error?

Hi Mauricio, we noticed this yesterday, around 21 hours ago, decided to wait, but error persisted.

Hi Sanja, this looks related to how a saved filter attached to one of your dashboards is being reconciled with your workspace hierarchy when the LDM is saved/updated, and it seems to be getting stuck in a conflicting state. A couple of things that would help: 1. Could you check the dashboard with ID

83c5e64f-4bd5-4f02-8742-016ea03845de

(it may sit in a linked/child workspace) and see what filter is saved on it by default? Try removing or resetting that saved filter, save the dashboard, then retry the LDM save. 2. Did you or your team make any changes to that dashboard, its filters, or your workspace hierarchy (child/linked workspaces) around Aug 6, right before this started? Please, let us know if 1) works. We'll keep looking into this on our end too.

Hi Mauricio, thank you very much for the help, it works now. The whole dashboard was corrupted, it was not allowing me to save any changes. What I did: • Created a copy of the same dashboard. Edited filer, saved without problems. • Deleted a corrupted dashboard

83c5e64f-4bd5-4f02-8742-016ea03845de

• Introduced the change in logical model, and saved a model without any problems.

Hi Sanja, that's great to hear — thank you for confirming, and for the clear write-up of exactly what you did! We don't have full confirmation yet of exactly what sequence creates that duplicate link in the first place — we're tracking this internally as a bug so it can be fixed at the source rather than needing this workaround. Since you mentioned you've hit this same pattern before on another dashboard: if anything comes to mind about what was done to either dashboard beforehand (e.g. it being duplicated earlier, a filter being removed/re-added, moving it between workspaces), that detail would genuinely help our engineers pin down the trigger. Thanks again for your cooperation in here 🙂

Will do 🙂 Just remembered one detail: in both cases dashboards were private.

Hi Sanja we truly appreciate this. We will include this in our bug report, and with this we have a clue to try to reproduce. One more question, how are you creating the dashboards? Are you, somehow, manipulating the metadata of the Dashboard or workspace using the APIs, by doing some put/push, etc, or you are simply using the UI?

Simply using UI

Hi Sanja, please apologies our back and forth, but we would like to know one more detail.. can you check, if possible when the dashboard were created, roughly? Were they created before June? Also do they have more than one Tab? If you still have the JSON saved of one old failed dashboard, we would appreciate if you can share it with us. Please use DM to share it. Thank you.

No worries 🙂 for the

83c5e64f-4bd5-4f02-8742-016ea03845de

i remember being created in 2024, and also modified same year. This one with JSONs compared, no clue when it was created, i remember one of our clients created it, and they had problem on May 19th. Both dashboards s had only one tab.

83c5e64f-4bd5-4f02-8742-016ea03845de

had only one visualization, the one from May had 3 or 4 visualizations. Will try to find the JSONs, but I'm not sure I saved them.

Thank you Sanja, with I will provide all this information, for the further investigation.

Found corrupted and working copy from May case. I will send you JSONs in DM, if this is ok?

Yes please 🙂