Discord Delivery

Discord Delivery

Use after channel-debug-core for Discord issues.

Files

• src/app/api/channels/discord/webhook/route.ts
• src/server/channels/discord/**
• src/server/workflows/channels/drain-channel-workflow.ts
• src/server/admin/why-not-ready.ts
• src/app/api/channels/summary/route.ts

Runtime Path

Discord interaction -> /api/channels/discord/webhook -> Ed25519 signature validation -> PING type 1 or deferred type 5 -> workflow -> reconcileDiscordIntegration -> native forward to port 3000 /discord-webhook -> interaction edit or channel fallback

Parallel Lane Inputs To Consume

Before proposing a Discord fix, consume:

• Vercel/app logs lane: interaction accepted/deferred, reconcile logs, requestId/deliveryId/interaction ID, and project targeting proof.
• Sandbox runtime lane: port 3000 listener and /discord-webhook evidence when native forwarding occurred.
• Workflow lane: drainChannelWorkflow run ID/status/steps, token-age evidence, final edit/fallback attempt, with verified project targeting when .vercel/project.json differs from the incident target.
• Prior-fix comparison: type 5 defer mistaken as completion, token expiry, reconcile failure, workflow forward failure.

Special Checks

• Returning type 5 proves only defer, not final reply.
• Interaction token budget matters; check preempt/fallback logs.
• Soft deadline is around 13.5 minutes in workflow logic.
• Reconcile failures can be causal.
• User-visible reply evidence must include interaction edit or channel fallback outcome.
• If a fast path is added later, apply channel-forward-parity.