Hey team, <based on this message>, I tried switchi...
# gooddata-cloud
e
Hey team, based on this message, I tried switching to the API call instead of the SDK, but I'm now getting a
500 Internal Server Error
with request id:
56960887-1906437
The API call seemed to work fine initially, but this error is new. Any ideas on what might be causing it?
j
Hello Evangelos, you say that it had been working without issues on your end, correct? Could you please define what has changed before seeing the error?
e
Hey Joseph, basically nothing changed. Last time I checked it was Friday afternoon (it was working back then), and when I checked this morning, I got the error message.
m
Hi Evangelos, I want to let you know that we're currently investigating why the API endpoing is not working. So far we've traced back the issue to some changes introduced recently. We'll keep you posted with more details as soon as they become available.
e
An update on my side that the API worked properly today.
e
I’m having the same
500 Internal Server Error
problem using the dependentEntitiesGraph endpoint:
Copy code
{
  "timestamp": "2024-10-31T14:26:58.426+00:00",
  "path": "/api/v1/actions/workspaces/2d1cc634-ba6e-4769-a4de-f678741f48f2/dependentEntitiesGraph",
  "status": 500,
  "error": "Internal Server Error",
  "requestId": "9947b6c5-237507"
}
I get a successful response from other API endpoints, e.g.
/api/v1/layout/workspaces/{{workspace}}/analyticsModel
@Moises Morales Any more information on this problem?
m
As far as I understand from our internal ticket, the issue happens under specific scenarios, unfortunately at this time, I wouldn't be able to provide an ETA for the resolution. You may try opening an insight from the UI/Analytical Designer and call again the endpoint. It may or may not help resolve the issue. My apologies I cannot help further at this time, but we will keep you posted with any details about the resolution.
👍 1