Get help on Discord

Getting React error when trying to create new team in Sanity

4 replies
Last updated: Apr 20, 2023
When I visit https://www.sanity.io/manage/create-new-team I am getting a React error. I tried both Chrome Version 112.0.5615.121 and Safari. What is the best way to escalate to get passed this so I can setup our org?
AI Update

I'm sorry you're hitting a React error when trying to create a new team! That's definitely frustrating when you're trying to get your organization set up. Here are the best ways to escalate this and get unblocked:

Immediate actions:

  1. Contact Sanity Support directly - Visit sanity.io/contact and use the "Account support" option to submit a request. This is specifically for help with billing, quotas, plans, and user management issues like yours. Include:

    • The exact error message or a screenshot
    • Both browser versions you tested (Chrome 112.0.5615.121 and Safari)
    • The URL where the error occurs
    • Any console errors if you can grab them (F12 → Console tab)

  2. Join the Sanity Community Discord - The team is very active there and can often help troubleshoot quickly. Visit sanity.io/community/join to get an invite. Note: Sanity recently moved from Slack to Discord for their community support.

  3. Check the status page - Visit status.sanity.io to see if there are any ongoing platform issues affecting the management interface.

Why this matters:

Since you're blocked from creating a team/organization, this is preventing you from even starting with Sanity. The support team should prioritize this type of issue since it's completely blocking. They may be able to manually create your organization or identify if there's a broader issue with that page.

For fastest resolution: I'd recommend doing both #1 (submit a support request) and #2 (join Discord) simultaneously. The Discord community might give you a quicker initial response, while the official support ticket ensures your issue is properly tracked and escalated if needed.

Show original thread
4 replies
Thanks for flagging. Are there any errors in the console? It’s also a long shot, but have you enabled cookies for the site?
Thanks. Here is the console error. I logged out, cleared the application cache and logged in again. I also tried a Chrome incognito browser. Same behavior
Error: Minified React error #301; visit https://reactjs.org/docs/error-decoder.html?invariant=301 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at oo (react-dom.production.min.js181)
at Ao (react-dom.production.min.js260)
at Ki (react-dom.production.min.js400)
at Lu (react-dom.production.min.js347)
at Nu (react-dom.production.min.js278)
at Pu (react-dom.production.min.js138)
at bu (react-dom.production.min.js163)
at react-dom.production.min.js115
at t.unstable_runWithPriority (scheduler.production.min.js343)
at Ql (react-dom.production.min.js325)
at Yl (react-dom.production.min.js61)
at Kl (react-dom.production.min.js428)
at hu (react-dom.production.min.js203)
at To (react-dom.production.min.js408)
at t._next (useObservable.ts9)
at t.__tryOrUnsub (Subscriber.js16)
at t.next (Subscriber.js22)
at t._next (Subscriber.js26)
at t.next (Subscriber.js18)
at t.notifyNext (mergeMap.js26)
at t._next (innerSubscribe.js21)
at t.next (Subscriber.js18)
at t._next (Subscriber.js26)
at t.next (Subscriber.js18)
at t._next (map.js26)
at t.next (Subscriber.js18)
at t.next (Subject.js25)
at t.nextInfiniteTimeWindow (ReplaySubject.js31)
at Object.next (shareReplay.js29)
at t.__tryOrUnsub (Subscriber.js16)
at t.next (Subscriber.js22)
at t._next (Subscriber.js26)
at t.next (Subscriber.js18)
at t._next (Subscriber.js26)
at t.next (Subscriber.js18)
at t.next (Subject.js25)
at t.nextInfiniteTimeWindow (ReplaySubject.js31)
at t._next (Subscriber.js26)
at t.next (Subscriber.js18)
at request.ts20
at Object.publish (index.js22)
at index.js27
at index.js16
at browser-request.js5
at h.<computed> (browser-request.js5)
at XMLHttpRequest.<anonymous> (instrument.js41)
This issue resolved itself and worked today still with Chrome 112.0.5615.121. The one difference I just realized is that I was no longer on VPN.
Ahh interesting, thanks for taking the time on the call and for the clear follow up, you rock 🤘

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Get started for freeExplore the demo

Was this answer helpful?