Why does my event debugger show that the queryID might not be consumed by a downstream feature?

When reviewing your Events Debugger, you may come across the message:

This event may still not be consumed by the destination if its queryID does not match any queries' queryID.

This indicates that even if a queryID is present in your event, it must exactly match the queryID generated by the corresponding search request. If there a mismatch, the event won't be used by downstream features such as Dynamic Re-Ranking. 

To quickly verify if the queryID in your event is valid:

1. Open the Events Debugger in your dashboard
2. Select a recent event
3. Go to the Query details tab

If the queryID is valid, you will see the associated query request and response

If nothing is shown, it may mean:

• The queryID is invalid, or
• The query is too old (only the last 1000 queries can be matched, which can affect high-traffic indices)
• You are on our Dynamically Scaling Infrastructure

Validate queryID consistency between frontend and debugger

If you have high-traffic volume, the most reliable way to confirm a match is to look for an event using a queryID taken from your frontend:

1. Open your browser’s Network tab

2. Filter requests by “Algolia”

3. Perform a search on your frontend

4. Locate the search request and copy its queryID

5. Go to the Events Debugger

6. Search for this queryID 

This should return the corresponding click or conversion event