Hi Vercel team,

We are testing a second Slack connector in a private, internal-only channel before allowing any external users or data.

Configuration

• Vercel Connect Slack connector on a Pro team
• Project is connected for Preview and Development
• Trigger destination targets a persistent staging branch
• Destination path: /eve/v1/slack
• The Slack installation succeeds and the app is present in the test channel
• Seven Slack trigger events are enabled

Observed behavior

• Fresh synthetic app_mention events appear in Connect Usage as inbound triggers
• The new connector shows 2 inbound triggers
• The configured destination remains at “No data” and Forwarded Triggers remains empty
• The destination deployment receives no request
• An established Slack connector targeting the same project, branch, and path has successfully forwarded events

Expected behavior Eligible inbound Slack events should be forwarded to the configured branch destination, where our runtime will apply its own fail-closed authorization and kill-switch checks.

Troubleshooting already performed

• Recreated the connector and reinstalled it to the Slack workspace
• Reconnected the project and recreated the trigger destination
• Confirmed the destination path and branch target
• Sent a fresh synthetic mention after installation and destination setup
• Kept the runtime disabled and kill-switched; no model, tool, API, or data mutation was attempted

Could you help us understand why Connect records the inbound Slack events but does not forward them? Is there a propagation delay, an additional event-routing setting, or a diagnostic showing why a received event was not matched to the destination?

I have intentionally omitted connector, app, project, workspace, and deployment IDs from this public post, but can provide them privately to Vercel staff if needed.