Hi team, we're getting `500 Server Error: Internal...
# gooddata-cloud
e
Hi team, we're getting
500 Server Error: Internal Server Error
when trying to export PDFs via the API (Note: Exporting via the UI for the same WS and dashboard works as expected). An example of a failed request below:
Copy code
<https://data.park46.se/api/v1/actions/workspaces/sbb/export/visual/cbcd0ea2d3620de94873d4090a8c1bf2f63ff367>
Can you please check it out?
m
Hi Evangelos, Thank you for this, we have been checking and we can identify all the 500 errors. Can you please, also send a direct link to the insight or dashboard you are trying to export (feel free to use DM). I will forward your request to our technical team for further investigation.
e
DM sent😊
✅ 1
m
Hi Evangelos, just to be sure, can you try now? I have just tried, after impersonation and I am able to export the dashboard in PDF by API. Can you also let us to know how you are trying to export the PDF, which endpoints and body?
e
I think that is the problem: the fact that the response depends on whether the platform has "available resources". Whenever we try this outside of working hours (8-17 Europe/Stockholm), everything works as expected.
d
Hello Evangelos, There was an overload on a memory component on 7.07 and 08.07. However, the one yesterday was bigger. We identified an addressed this issue. Since yesterday is back to normal. Also, I’ve been checking our logs and so far I don’t see any other occurrence after yesterday. However, let me know if you see it again.
e
Hey @Daniela Salmeron, thanks for getting back to me. Probably my script is responsible for this behavior. I'm trying to export dashboards from basically all of our workspaces and some of them fail by giving us the
500 Internal Server Error
message. I guess the endpoint cannot handle this. How should we approach the issue? What are the best practices of exporting multiple PDFs?
d
Hello, This was an unfortunate bad timing with a new service we were trying to deploy. We were performing a slow rollout into production at the same time you did this action. However, after the spike, we rolled back and now we are performing more test in our dev envs to include more scenarios. In general, best practice is just not to go over the Platform Limits, which for exports is: 10 simultaneous export tasks. If you hit the error again, please let us know 🙂 we can check if there’s anything else returning this errors.
e
Thanks for the clarification, @Daniela Salmeron! That makes sense. We'll update our script to respect the 10 simultaneous export limit and monitor from our side. Will reach out if the issue comes up again.
d
Sure thing! Thank you!