pull_request webhooks contain inconsistent data #28877
Unanswered
jeyq
asked this question in
API and Webhooks
Replies: 2 comments
-
This is also affecting us. Any updates on this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
This is affecting us now and hindering our ability to seamlessly run our external pipeline. Any updates? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
we're seeing inconsistent data in pull request webhooks. Sometimes when we receive a
pull_request
webhook withclosed
action, theclosed_at
field in the payload isnull
. Also, it seems like theupdated_at
timestamp in the payload for pull_request doesn't account for the change that triggered this webhook. And, thestate
field also isopen
even if theaction=closed
In these cases it also seems that when we then fetch the PR information from the GraphQL API immediately, it also doesn't represent the latest state info. After a while, we then get the up to date information from the API.Most of the times the information is consistent but it seems that there's still non-trivial amount of webhooks we get that have this consistency problem.
Is there something we could do to avoid this and ensure we get the latest up to date information about the pull request in the webhooks?
Beta Was this translation helpful? Give feedback.
All reactions