Hello. My employer sent me a link to join their workspace. I was able to successfully sign up, but when I log in, the timer page is blank and I can’t seem to do anything. I’ve tried refreshing, opening in a new browser, and deleting cache. I have also tried logging in with both the desktop and mobile apps and I am unable to login at all with these. Can someone please help me fix this issue?
Hello! We’ve got our team looking into this and will respond here when we get more information from our team!
1 Like
Same issue here.
I’ve used Toggl a few years back. Workspaces got deleted due to inactivity. Decided to use it again on a new project and was met with the blank page issue.
I’ve deleted browserdata and cookies, to no avail.
I do get a 403 in the console which might be a permissions issue on my account.
Post Title: New account stuck on a loading page.
Your Question/Topic: I created my first Toggl account this morning and having the same issue.
Currently am only able to go from Log in > Create new Organization Give your Organization a name. Don’t worry, you can change it later > Invite others to your Organization You can invite up to 4 people using their email address. Later, you can invite and manage all your members in the Teams page > Loading page with an empty background and a circle loading symbol with url ending in /organization/new/invite. Only able to click on “Timer” (which is also a empty page) or “Profile”.
I have tried:
-
Waiting on the page to load - Continuous loading circle symbol (for hours)
-
Refreshing the page - Starts off blank, then after a few moments shows the “Create new Organization**”** page again. Same results when going forward.
-
Entering different Organization names - Same results.
-
Entering emails for invites or skipping - Same results.
-
Made a new account with a different email not connecting through a Google Account - Same results.
-
Logged in on Mac iOs desktop version - Error “Oops, something went wrong. Invalid full sync response received”.
Heya everyone 
@Rachaels @ggal @Sebastian_Nord this should be resolved now and a quick browser refresh should do the trick.
1 Like