Unable to create a context after org rename


#1

I get the following error:

Uncaught (in promise) Error: GraphQL error: Non-nullable field was null.
GraphQL error: Internal conflict found.
at new t (frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8911)
at Object.next (frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8911)
at m.next (frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8948)
at frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8911


Unable to view contexts in UI
#2

FYI this is blocking our ability to run builds and deploy.


#3

In what circumstances do you get that error?

I can’t recall where organisations are added in the UI, but is it possible in your case to remove it and re-add it? Sometimes that gives it the necessary turn-it-off-and-on-again to get it working.


#5

Hi Kyle,

This did not fix our project. Builds are getting kicked off okay however we cannot add contexts which results in all of our builds failing

I cannot add a context because I get the following error on: https://circleci.com/gh/organizations/boundless-inc/settings#contexts

Uncaught (in promise) Error: GraphQL error: Non-nullable field was null.

GraphQL error: Internal conflict found.

at new t (frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8911)

at Object.next (frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8911)

at m.next (frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8948)

at frontend-production-1e6b8b8cb1ff30c71e6bd8ec81a56730.js:8911

This is blocking all of our builds (even branch builds that do not need the context fail)

As you are likely aware contexts are on an organization not a repository.

Nolan


#6

Halfer it happens after I renamed the org in github.

There is nothing in the circle ci UI to delete an organization. This is also tied to billing, wouldn’t be a huge fan of paying circleCI twice in one payment cycle as well (I don’t believe months are pro-rated). But assuming circle would credit us there is no way to delete/re-add the org that I can find.

Even though context’s aren’t used by our branch builds circle CI errors out saying it can’t find the context and we can’t add any contexts. The only option we have right now is it use another CI provider.


#7

Hi from the CircleCI team –

Closing the loop here. This is a known issue, and so if this is happening to future readers, please reach out to our team with your org name. There is a manual workaround we can do to help you solve this and move forward.

Thanks all,

Emma


#8

I have the same issue with my org… Here’s the error:
Uncaught (in promise) Error: GraphQL error: Non-nullable field was null.
GraphQL error: Internal conflict found.
at new t (frontend-production-63965b2dc5493c412703ba468451ebeb.js:8911)
at Object.next (frontend-production-63965b2dc5493c412703ba468451ebeb.js:8911)
at m.next (frontend-production-63965b2dc5493c412703ba468451ebeb.js:8954)
at frontend-production-63965b2dc5493c412703ba468451ebeb.js:8911

My org name is gsa-team


#9

I would suggest getting in touch with the team via email (explore the main site for an address to use).


#10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.