Can the events api "miss" events on a given pull

[niallscc]

Select Topic Area

Question

Body

As is stated in the API docs, events may be delayed by between 30s and 6hrs, but if we get an event at time T does that mean that we are guaranteed to have received all prior events to T, or could there still be events in the queue that would be missed if we pulled again and filtered to only events past time T?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[devSerays]

As of December 2024, the GitHub Events API does not guarantee the order of event delivery. Events may be delayed between 30 seconds and 6 hours, and receiving an event at time T does not ensure that all prior events have been delivered. Therefore, if you pull events at time T and filter for events past T, you might miss some events still in the queue.

To mitigate this, consider implementing idempotency in your event processing to handle potential duplicate events gracefully. Additionally, regularly polling the API and maintaining state can help ensure that all events are processed, even if they arrive out of order.

For more details, refer to GitHub's documentation on webhook events and payloads.