What Does the Error "Sync Token is No Longer Valid, a Full Sync is Required" Mean?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

what does this error mean “Sync token is no longer valid, a full sync is required.”?

2

This error message “Sync token is no longer valid, a full sync is required” typically indicates that the sync token you’re using for an API has expired or become invalid. To resolve this issue, you’ll need to perform a full sync, which usually involves fetching all the data again and obtaining a new sync token. The process for doing a full sync may vary depending on the API you’re working with. Please provide more information about the API or service you’re using, so I can help you with the specific steps to resolve this error.

3

This is for a google calendar API

4

Hm that’s strange, I haven’t seen that before. Can you try reconnecting your Google Calendar account? And can you let me know where you’re seeing that error message?

5

Yea it’s working after I went to Edit and reselect accounts. A couple observations.

  1. It was failing “silently”. There was nothing in event history and I had to go to logs, which is kinda hidden, to see the error
  2. Reconnecting is not very obvious. Is it simply clearing the selection? Refreshing field? etc.
6

The error:

2023-08-14T08:12:12errorError: Sync token is no longer valid, a full sync is required.
at makeErrorObservation (/var/task/node_modules/@lambda-v2/component-runtime/src/makeErrorObservation.js:7:11)
at /var/task/index.js:124:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async Runtime.exports.main [as handler] (/var/task/index.js:60:20)

7

Yea, the silent failure is frustrating. I’m not sure what the issue was there. Was that error on an action or source?

8

I just had the exact same happen with my google calendar. Events weren’t coming through to trigger the workflow and the only indication was my own observation.

logs: 2024-08-16T11:39:02error

Error: Sync token is no longer valid, a full sync is required.

at makeErrorObservation (/var/task/node_modules/@lambda-v2/component-runtime/src/makeErrorObservation.js:7:11)

at /var/task/index.js:124:30

at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)

at async exports.main [as handler] (/var/task/index.js:60:20)

Solution: I added a second duplicate trigger, tested it, and then deleted the old trigger.

It would be super helpful if the trigger could handle the error without the need for intervention or if I could receive a notification alerting me to the error.

9

Agreed 100%! Here’s the issue we’re using to track this feature request!