flo all the sudden stopped auto emailing

[tallpr24]

My flow has been functioning flawlessly until approximately two weeks ago. I had configured it to send the reports daily at 7 AM. However, it has ceased to do so. I can execute it manually, and I receive the emails without any problems. Nevertheless, the automatic email feature is no longer operational. Does anyone have any insights or recommendations on how to resolve this issue? I do not see any errors, and it still indicates that I am logged into Gmail, as I am able to run it manually and receive the emails.

[tallpr24]

Im worst off now, now it dont even work.

[tallpr24]

i put it back to testing, and now it doesnt work at all on neither testing or published.

[tallpr24]

he initial problem I encountered was that it consistently generated errors in the logs. Consequently, I adjusted the frequency to send the three flows every hour instead of consecutively, which appeared to resolve the issue. However, another problem persists, similar to what occurred last night, where it indicated that the token had expired. It seems that I need to log back into Gmail every few days to resynchronize and obtain a new token. Once I completed that, it began functioning properly again. Is this behavior considered normal?

[Vicente_SC]

Is your Gmail app currently set to the "testing" audience?  If the audience for the app is set to "testing", the access token will only be valid for a few days.  If that's the case, publishing the app should allow for longer-lived tokens. Here there is some information about Google publishing status: https://support.google.com/cloud/answer/15549945?sjid=10313091329646675771-EU#publishing-status&zipp...

[tallpr24]

yes it was set to testing. i just clicked on publish.  will that resolve the issue?

[tallpr24]

so i published it, and now it doesnt work, i cant even run the flow manually, i broke it by clicking publish.  is there another step after publishing from test i need to do ?

[Vicente_SC]

Hi @tallpr24. I think I identified your workflow and logs, and I see an invalid credentials error. Today, that workflow ran successfully. Did you make any changes? Is the issue now solved?