Error syncing entry: Unexpected "tags" type object, offset=233. Restricted

[rmorales]

I get an error when creating a time entry that I cannot longer modify.

I have created an entry using the web interface, and not it is marked as Restricted with a warning icon. If I move the mouse pointer over the icon I get the message:

Error syncing entry: Unexpected “tag” type object, offset=233. Try again

The Try again includes a link, but it does nothing.

I have created a second entry with exactly the same information and it has been marked as Restricted to, but I can create other entries without problems.

What is it wrong?

Regards.

[Adam_Beltz]

Our users are also getting this error

[ago]

Also getting this error and having the same issue. I contacted support but no reply so far.

[Jake]

Hey folks! This is a known issue and our devs are working on it! Expect an update from me when we get it fixed.

[Jake]

Hello,

Thank you so much for the wait on this! I just wanted to share a quick update regarding your issue with tags. Our team has issued a fix that should address the majority of users who are experiencing this issue!

To ensure you get the fix in place, please note down any unsynced entries that may currently be present, then refresh your browser. For some users that find that this hasn’t worked, clearing your browser cache and cookies may help as well.

Please note that, in our efforts to fix this bug, there is a chance that a previous UI glitch may still be present where adding tags to an entry may cause the tag dropdown menu to not show the selected tags at the top of the list (as is our standard practice). Regardless of this, clicking outside of the tag dropdown should show that the tags have still been attached successfully to the entry itself, as the tag names should appear in their proper place to the right (or underneath, if in Calendar mode) of the time entry description. This UI glitch is something we are still working on, but wanted to ensure that you were aware that the more pressing tag issues have now been cleared.

Thank you once again for your patience while we worked on this!

Best,

[Noreen]

I am having this one and this creates massive issue for me

[Noreen]

I have done everything and still not working - I am in deep trouble with my client if this cant be resolved. Please can you help?

[Jake]

Hi @Noreen I’m hearing from our team that this should be resolved Can you verify you’ve cleared your browser cache and cookies?

[Noreen]

Hi Adam,

Yes I have cleared my cache and the browser and also restarted my lappie

[Jake]

Sending you a DM to get some of your account info

[Vedran_Karacic]

Same is happening to me, I have the cache and cookies cleared but whenever I try to stop the currently running task I get that error:

The task is now running for 65 hours, although I don’t see it in my Android app.
I’m using Brave Browser Version 1.77.97 Chromium: 135.0.7049.84 (Official Build) (64-bit)
If that helps.

This is the request payload when I try to stop it:

The request is a POST to https://track.toggl.com/api/v9/time_entries?meta=true

[Vedran_Karacic]

Okay, clearing cookies, local storage and session storage seems to do the trick.