This issue is likely caused by the database connection (e.g., PostgreSQL) timing out after a period of inactivity, which results in the Phoenix application not properly handling reconnection when user interaction resumes. Users then see an error and must refresh or log in again. The recommended first step is to check your database connection settings (timeouts, pool size) and ensure Phoenix is configured to handle idle connections gracefully. Refreshing the page typically resolves the error, confirming it's a session/connection issue rather than an application bug. See the detailed discussion and error trace in <https://github.com/Arize-ai/phoenix/issues/7337|this GitHub issue>.
Would you like more detail on how to adjust your database or Phoenix settings to mitigate this problem?
Sources:
- <https://github.com/Arize-ai/phoenix/issues/7337|bug UI Error After Period of Inactivity>
