discord.js v14 gateway Client and MessageComponentCollector: who acknowledges component interactions within three seconds?

Answer

In discord.js v14 stable, MessageComponentCollector does not automatically acknowledge button or select-menu interactions. The gateway Client emits INTERACTION_CREATE events, and the collector filters them by message, component type, and customId, then emits collect or collectable. It never calls deferUpdate(), update(), reply(), or deferReply() for you. Application code must acknowledge within Discord's approximately three-second deadline, or the user sees 'This interaction failed'.

Confirmed facts

• MessageComponentCollector only filters gateway events and emits lifecycle events; it does not acknowledge interactions.
• Discord requires a valid response to every component interaction within about three seconds.
• Valid acknowledgement methods include deferUpdate(), update(), reply(), and deferReply().

Likely explanation and risks

The collector has no ownership or deduplication model. If two collectors match the same message and customId, both can receive the same interaction. The library does not coordinate which one responds, so duplicate acknowledgements can trigger 'interaction already acknowledged' errors. A shard reconnect can also interrupt pending handler execution and increase the chance of missing the deadline.

Steps for this case

1. Acknowledge immediately inside the collect listener, before any asynchronous work:

2. collector.on('collect', async interaction => {
     await interaction.deferUpdate();
     // perform work after acknowledgement
   });

3. Use only one collector per message and customId, or track handled interaction IDs in a Set so only one handler responds.
4. Keep heavy work after the initial acknowledgement; do not await long operations before calling a response method.

Assumption: you are using the stock discord.js v14 MessageComponentCollector, not a custom subclass or wrapper. A wrapper could intercept collect and acknowledge on your behalf, which would change these steps.

Verification: add a collect listener that logs the interaction ID and timestamp, then intentionally omit deferUpdate() or similar. If Discord reports 'This interaction failed' after roughly three seconds, the collector is not acknowledging automatically. Confirm the installed version with npm list discord.js.

Missing diagnostic detail: are you using a custom collector subclass or wrapper that might acknowledge interactions? This changes whether application code must handle acknowledgement.