Bug Report: Deleted Custom Provider Still Active and Intercepting All Requests

[MarkusThomas257]

Summary
A deleted custom provider continues to intercept all API requests even after deletion. The provider cannot be removed from the routing system.

Environment

• Manifest Agent: Nummer 5
• Affected Provider ID: custom:400ebd9f-3922-4749-b0e3-feabe91d26ae
• Date of issue: April 17, 2026

Steps to Reproduce

1. Create a custom Gemini provider in Manifest
2. Delete the provider via the Connections UI
3. Create a new custom Gemini provider with the same Base URL but a valid API key
4. Update routing to use the new provider
5. Send any API request via the Manifest endpoint

Expected Behavior
Requests should be routed to the newly created provider with the valid API key.

Actual Behavior
All requests are intercepted by the deleted provider 400ebd9f-3922-4749-b0e3-feabe91d26ae regardless of which model or provider is specified in the request:

json
{
"error": {
"message": "Bad request to upstream provider",
"type": "fallback_exhausted",
"status": 400,
"primary_model": "custom:400ebd9f-3922-4749-b0e3-feabe91d26ae/gemini-2.5-flash-lite",
"primary_provider": "custom:400ebd9f-3922-4749-b0e3-feabe91d26ae"
}
}

This happens even when specifying completely different models:

• model: auto
• model: gemini-2.5-flash-lite
• model: google/gemini-2.5-flash
• model: meta-llama/llama-3.3-70b-instruct:free
  Impact
  The Manifest endpoint is completely unusable. All requests fail with HTTP 400 because the ghost provider has no valid API key.

Workaround
None found. Forced to bypass Manifest entirely and connect directly to OpenRouter.

Request
Please permanently delete provider 400ebd9f-3922-4749-b0e3-feabe91d26ae from your backend and clear any associated routing cache for my account.