Could not resolve to a node with the global id of '******'
See original GitHub issueI have a github workflow using this action that adds all issues with a bug
label to my project board. I’ve configured the workflow in two repos with the same github token available to both (via organization secrets).
In one repo the action is working correctly. In another I am seeing this error:
Could not resolve to a node with the global id of '******'
I’ve hidden the id value from the error cause I don’t know if that’s sensitive or not. The id is meaningless to me and looks like some opaque identifier.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Use of team-reviewers results in: "Could not resolve to a node ...
This looks like a permissions issue. Could you explain a bit more about your setup. Is the team in the same org as...
Read more >Update github repository description via graphql
I'm getting this error message: "message": "Could not resolve to Project node with the global id of 'MDEwOlJlcG9zaXRvcnkxMTY0ODYzMDc'.",. What ...
Read more >GraphQL global ID migration update - The GitHub Blog
All newly created GraphQL objects now have IDs that conform to a new format, which we refer to as "next IDs." Learn how...
Read more >File: Handling-errors — GraphQL::Client master - Doc Index
"Could not resolve to a node with the global id of 'abc'" message = data.errors[:issue].join(", ") render status: :not_found, plain: message end ...
Read more >absinthe_relay_oxo v1.2.1 Absinthe.Relay.Node - HexDocs
Node. Support for global object identification. ... global ID. The node field should be defined within your schema query and should provide a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
👋 We are currently working on deploying some internal security policy updates that we think might be related to this issue. We are tracking this issue in our internal backlog and we’ll let you know when we have any updates.
In the meantime, for anyone who has been experiencing this issue (@defunctzombie @jlind23 @momobel), could you provide more information on your setup? The following would be helpful:
Thanks @fidou ! That solved it for us. Also to note, you need to re-authorize the org after a token change.