[Cloud Runtime P0] Stale conversationIdle120000/300000 metadata causes every message_created event to fail

Severity

Production P0 — every incoming message_created event fails inside Botpress Runtime before the production handler can execute.

Affected existing bot

• Workspace ID: wkspace_01M1ZTMDCPPE6E86FY2XE5TWBH
• Bot ID: 9577762f-b864-4cff-813c-a27920ab663b
• Bot type: existing ADK / Vibe production bot

Direct production evidence

Botpress Inspect → Events shows incoming message_created events reaching this exact bot, then failing with both of these runtime errors in the same production time window:

[Runtime] State "conversationIdle120000" of type "conversation" isn't defined for the bot "9577762f-b864-4cff-813c-a27920ab663b"

[Runtime] State "conversationIdle300000" of type "conversation" isn't defined for the bot "9577762f-b864-4cff-813c-a27920ab663b"

The presence of two different generated inactivity-state names for the same bot/time window indicates stale or conflicting lifecycle/inactivity metadata rather than a single missing application state.

Temporary manually-created workaround states were removed. The failures persist afterward. Incoming channel delivery is confirmed; execution fails before the ADK conversation handler and before any downstream HTTP call.

Impact

• All production Messenger messages fail before handler execution.
• The bot sends no response.
• Downstream claim API is never called.
• Campaign remains OFF; no coupon issuance is involved.

Requested Botpress action

Please inspect and safely reconcile the server-side Runtime/Vibe lifecycle metadata and active production deployment definition for this existing bot, including any stale compiled deployment/router/cache records that still reference conversationIdle120000 and conversationIdle300000.

Please:

1. Confirm which active deployment/runtime metadata record is generating each state lookup.
2. Reconcile or clear only the stale lifecycle/inactivity metadata without deleting or recreating the bot.
3. Confirm the effective production state definition before and after repair.
4. Confirm new message_created events no longer fail on an undefined conversationIdle* state.
5. Provide a supported public API/CLI procedure if one exists for this metadata repair.

Safety constraints

Please do not:

• delete or recreate the bot;
• replace/reset channel integrations or OAuth authorization;
• alter ADK source, secrets, Meta configuration, downstream backend, database, or campaign state;
• recommend adding synthetic conversationIdle* states as a workaround.

No secrets or access tokens are included in this report.