perpetual full sync loop caused by 404 error from googleapiclient

[hugonobrega]

I am getting a perpetual pull: historyId is too old, full sync required. message followed by a (seemingly successful) full sync whenever I try to gmi sync

Digging through the code and printing the exception which triggers that message, I get

googleapiclient.errors.HttpError: <HttpError 404 when requesting https://gmail.googleapis.com/gmail/v1/users/<my-account-name>/history?startHistoryId=6874935&alt=json returned "Requested entity was not found.". Details: "[{'message': 'Requested entity was not found.', 'domain': 'global', 'reason': 'notFound'}]">

I don't think I did anything wrong in following the setup steps since the sync successfully downloads the messages and metadata (and things had been working fine for ages). Can something have changed on the Google side of things?

lieer 1.6
google-api-core 2.24.2
google-api-python-client 2.164.0
google-auth 2.38.0
google-auth-httplib2 0.2.0
google-auth-oauthlib 1.1.0
googleapis-common-protos 1.69.1
python 3.10.7

[gauteh]

Hm, weird. Anyone else experiencing the same thing?

[hugonobrega]

Update: the problem was with the historyId itself. I don't know how (maybe it was just too old?) but manually entering a "good" historyId in .state.gmailieer.json has made everything work again

In any case, it seems weird that the newest historyId wasn't being stored in the state file after the full sync that was happening before, seems like a bug?

[hugonobrega]

Sorry for the slight spam, but after some minutes, the state file is back to the bad historyId 6874935 (same as in the error in the first message) and we are back to the full sync loop