notice about recent task execution

[kumarbobbyldh]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzNTA0M2M1MjZhNTUzNjUxMzEi_pc

Your Task History ID

IjU3NjUwNTY0MDYzNjA0MzY1MjZjNTUzNDUxMzc1MTYzNTQzMzBmMzAi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

Hi,
I’m receiving an email notification about a recent task execution. However, my workflow is running correctly. Could you please explain why I’m getting this email, and how I can troubleshoot or verify what is triggering it?


This email is to notify you that for the workflow "Bewerbung form to Google Calendar (all forms)" , a recent task was not executed due to following error -

Task History ID: IjU3NjUwNTY0MDYzNjA0MzY1MjZjNTUzNDUxMzc1MTYzNTQzMzBmMzAi_pc
Step Name: Google Calendar > Get Event by ID
Connection Name: Google Calendar #14
Task Error Detail:

{
"error > code": 401,
"error > message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
"error > errors > 0 > message": "Invalid Credentials",
"error > errors > 0 > domain": "global",
"error > errors > 0 > reason": "authError",
"error > errors > 0 > location": "Authorization",
"error > errors > 0 > locationType": "header",
"error > status": "UNAUTHENTICATED"
}

 

[Preeti Paryani]

Hi @kumarbobbyldh,

Thanks for reaching out.

Upon checking, we noticed that the error occurred due to the OAuth-based Google Calendar connection. The access token for such connections is refreshed automatically in the background. At the time this task executed, the token had temporarily expired, which caused the authentication error.

Please note that the workflow was auto re-executed within a few minutes, and it ran successfully once the token was refreshed. This is why you received the notification, even though the workflow is now working correctly.

No action is required from your end in this case. The issue resolves itself automatically.

We hope this clarifies the reason behind the notification.