Unable to create new branch
Hello,
When I try to migrate the schema from my dev branch to my main branch, I get this error:
The same error happens when I try to create a new branch
13 Replies
Hi there, can you please activate support access to your workspace so I can take a look? You can do so via workspace settings.
https://support.xata.io/hc/en-us/articles/16775415603997-Allowing-Support-to-access-your-Xata-Lite-Workspace
I can see that your cell is referring to a dedicated cluster but you are currently on the Free plan. The cluster looks to have been terminated.
Xata.io Support portal
Allowing Support to access your Xata Lite Workspace
In the Xata Lite Workspace Settings page you will find the toggle "Allow support to view your workspace".
Enabling this allows Xata Support to access your Workspace with full read and write rights ...
Hello, I’ve enabled it
Thanks, I'll take a look now
Which database is this affecting?
globiothec2
Hi, any updates?
Still investigating, thanks for bearing with me 👍
Hi, thanks for your patience, can you please share the command you're using to migrate the schemas?
i was trying to use the UI
Ok thanks for the clarification, I've tried creating a new branch and I've run into the same issue. Will continue to investigate. Thanks for your patience.
alright, thanks
Good day, any progress on this matter?
We're still investigating, thanks for bearing with us.
Hey, @Kaligraphy thanks again for your patience. We've fixed the issue in the backend. I tested this by creating a new branch in
globiothec2 called support-test. It's currently taking some time to create the tables in the new branch so please let me know if you run into any other issues.i will give it a few minutes then try again
thanks
No problem. The initial request to make the branch might appear to hang but if you refresh the page you'll see the new branch created. The tables will take some time to appear as the migration history of the source branch is replayed.
I have been able to branch the database. It succeeded but displayed an error message "fetch failed" (this could be my own network) but the main issue has been fixed. I will disable workflow access and remove the test DB
Great glad to hear.