No way to link all webhook deliveries together using the available data from the API. I end up having to make too many API calls and exhausting the limits. #145246
Replies: 3 comments
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
After submitting this, I just realized that the GUID is the same for any redeliveries. I'm going to try using that. |
Beta Was this translation helpful? Give feedback.
-
Reopening: I still need the workflow IDs to match a subsequent "completed" with a "queue" to avoid redelivering the queued. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
There is no way to determine, quickly, without making an individual api call for every single webhook delivery, if a failed queued webhook delivery had a successful "completed" webhook delivery happen later on. We don't want to redelivery it or else it will orphan in the queue we keep of jobs needing processing.
Requesting the workflow_job delivery objects get the workflow run and job id attached. Really any ID at all that would allow me to tie all webhook deliveries together from the https://docs.github.com/en/rest/repos/webhooks?apiVersion=2022-11-28#list-deliveries-for-a-repository-webhook results would work.
Beta Was this translation helpful? Give feedback.
All reactions