search

appsmithorg / appsmith

Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
https://www.appsmith.com
Apache License 2.0
33.93k stars 3.66k forks source link

[Bug]: 503 screen when Appsmith tab is open for a long time in the browser #30610

Open mohanarpit opened 8 months ago

mohanarpit commented 8 months ago

Is there an existing issue for this?

Description

When Appsmith app is idle for a long time, the client shows 503 error screen even though no activity took place on that tab. I suspect some underlying API is failing & the client immediately redirects to 503 & never recovers from there. We should make the API more stable and also, the handling on the client more robust.

Steps To Reproduce

  1. Open any Appsmith app
  2. Walk away from the screen & let the app idle.
  3. Check back again after 3 hours. You will see a 503 error screen even though no activity took place on the tab.

Screenshot 2024-01-25 at 9 31 53 AM

Public Sample App

No response

Environment

Production

Issue video log

No response

Version

Cloud / Self-hosted

Nikhil-Nandagopal commented 8 months ago

@mohanarpit which team should own this?

jbaker43 commented 1 month ago

Is there any update on this? Our team is facing the same issue.

Nikhil-Nandagopal commented 1 month ago

@jbaker43 this was an intermittent issue that we weren't able to reproduce. Are you able to reproduce it?

jbaker43 commented 1 month ago

@Nikhil-Nandagopal yes. We are using appsmith for live dashboarding and every morning we are coming into the monitors displaying a 503 error.

jbaker43 commented 1 month ago

I should add that the data is refreshing periodically about every 5-10 minutes.

nidhi-nair commented 1 month ago

@jbaker43 would it be possible for you to leave your network console open overnight as well, and then share the information from in there when you see the 503? Would love to understand which of our APIs is crashing. We can set up a call to discuss this further once we have some headway here.

jbaker43 commented 1 month ago

@nidhi-nair Yes that is possible. What would the best way to do this be? Which logs do you need?

nidhi-nair commented 1 month ago

@jbaker43 we need information from your network console, so before you log out for the day, please turn the console tab on and share the list from the "Network" tab on the following day. It would be great if you could also share the logs from your instance. We have steps for acquiring logs documented here.

jbaker43 commented 1 month ago

Will do. I will post back here @nidhi-nair Thanks for the help!

mohanarpit commented 4 weeks ago

@nidhi-nair @ApekshaBhosale I think the reason for this error screen is because of the failure of the API /tenants/current. In the network console, I see errors related to FETCH_TENANT_CONFIG_ERROR. In the code, I can see that when this API fails, we trigger a "safe crash". If we handle the error to this API differently, I think this error screen will go away.