Workspace deleted - unknown error

Hi team, we were testing Twenty, and then we kind of got distracted and didn't look at it for a couple of weeks. Now I'm picking this back up, and trying to get started again. I tried logging in, and got 'unknown error'. I tried signing up again, and got 'unknown error'. I am happy to add my card and pay, I just don't know how to now!
11 Replies
Prastoin
Prastoin4w ago
Hey @pineapple, unfortunately any suspended workspace gets evicted after 14 days of inactivity You should still be able to re-create one though
pineapple
pineappleOP4w ago
Yeah I understand any suspended workspace gets evicted, but I was not able to recreate one Just got "unknown error" when I try to sign in or sign up
Prastoin
Prastoin4w ago
Where trying to sign in or signup
Prastoin
Prastoin4w ago
Please try signing up in https://app.twenty.com
Twenty
A modern open-source CRM
pineapple
pineappleOP4w ago
yep, that's the url I was using
No description
Prastoin
Prastoin4w ago
I guess you've been trying to signup or signin on your old workspace domain
pineapple
pineappleOP4w ago
yes, it's the same email
Prastoin
Prastoin4w ago
Could you please share any errors in the browser console ? Or share your email by dm
pineapple
pineappleOP4w ago
No errors in console. Failed to load resource: net::ERR_BLOCKED_BY_CLIENTUnderstand this error files/person-picture/original/7e4d491e-5482-4c9f-a490-a4d1b62da10f.38:1 Failed to load resource: the server responded with a status of 403 ()Understand this error o4505516959793152.ingest.us.sentry.io/api/4507072563183616/envelope/?sentry_version=7&sentry_key=f841f61cf36fe2016e8a79b8890aa88c&sentry_client=sentry.javascript.react%2F9.26.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTUnderstand this error o4505516959793152.ingest.us.sentry.io/api/4507072563183616/envelope/?sentry_version=7&sentry_key=f841f61cf36fe2016e8a79b8890aa88c&sentry_client=sentry.javascript.react%2F9.26.0:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT Sure Will dm you
Prastoin
Prastoin4w ago
Fixed manually as a workaround for the moment Fix should be released soon

Did you find this page helpful?