litellm - 💡(How to fix) Fix [Bug]: Prompts in Experimental not fetched when server shutdown [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#25631Fetched 2026-04-14 05:38:31
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
labeled ×1
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

Hi Team, The Prompts in Experimental section when created is stored in Postgres SQL tables and in memory registry but when fetched in UI/API through lists end point it fetches from only the in memory register. Now in scenario when the server is shutdown and restarted the in memory registry will not have the prompts so the UI renders empty while the same entry is persisted in Postgres SQL tables

Steps to Reproduce

  1. Create LITELLM prompt from experimental through UI/API
  2. Restart the LITELLM docker container hosted pod
  3. No prompts are rendered on UI.

What LiteLLM version are you on ?

v1.82.3

Twitter / LinkedIn details

https://in.linkedin.com/in/sumeetlalla1994

extent analysis

TL;DR

The issue can likely be resolved by implementing a mechanism to load prompts from the Postgres SQL database into the in-memory registry upon server startup.

Guidance

  • The root cause appears to be the loss of in-memory registry data upon server restart, while the data persists in the Postgres SQL tables.
  • To verify this, check the server logs for any errors or warnings related to data loading from the database upon startup.
  • Consider implementing a data loading mechanism that populates the in-memory registry from the Postgres SQL database when the server starts.
  • Review the existing code for any data synchronization or caching mechanisms that may be relevant to this issue.

Example

No code snippet is provided due to lack of specific implementation details.

Notes

The solution may require modifications to the server startup process or the data access layer to ensure that the in-memory registry is populated from the database.

Recommendation

Apply a workaround by implementing a data loading mechanism to populate the in-memory registry from the Postgres SQL database upon server startup, as upgrading to a fixed version is not explicitly implied in the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING