Request for Remote Session to Troubleshoot Automation Error Emails

Dear Team,

I would like to request your assistance regarding an issue I am facing with several of my automation flows. I am receiving error notification emails even though the automation flows are completing successfully without any issues.

I would like to demonstrate this issue to you through a remote session so that you can better understand the problem and help identify the root cause and provide a suitable solution. So, please arrange a remote session and inform me.

Regards,

Sandeep Banduni

+91 9824199313

Hello Sandeep,

To help us investigate this right away, could you please share a screenshot of the error notification email you received, along with the Workflow Name or Workflow URL where this occurred?

Having a screenshot of the email will allow us to see the exact error code or message and identify why the notification was triggered. Once we review these details, we will determine if a remote session is needed or provide you with an immediate solution.

Looking forward to your response so we can assist you promptly!

Dear Team,

Kindly find the required details and attahced images for your reference.

Purchase Order ABRL : https://connect.pabbly.com/workflow/mapping/IjU3NjYwNTY1MDYzZTA0M2Q1MjZjNTUzNDUxMzQi_pc

Hello Sandeep,
Thank you for providing the workflow links and screenshot.
Upon reviewing the error details from the screenshot for your workflow **"Purchase Order ABRL"**, we identified the exact cause:

The step Google Drive > Upload a File (Legacy) is using an outdated integration version/script connection (`Google Drive #42`). Google has updated its file access permissions, causing this legacy script connection to return a **400 error** ("Script ID could not be opened") when attempting to upload files.

How to Resolve It:

1. Open your workflow: Purchase Order ABRL.

2. Locate the Google Drive action step.

3. Update or re-select the action to the latest Google Drive (Non-Legacy / Standard) action event (e.g., Upload a File).

4. Click on Connect and establish a fresh connection with your Google Drive account.

5. Save the step and re-test the execution.

Please update the Google Drive step in this workflow (and check if the legacy step is used in your other two workflows as well). Once updated to the latest Google Drive action, the error emails will stop.

Let us know if you need any further assistance!

Sir,

Even though we are receiving this error email, the automation is still getting completed successfully, and the emails are also being sent properly along with the correct documents.

Could you please help us understand why this error is occurring despite the automation completing successfully?

Hello Sandeep,

You are completely right in observing that the emails and documents are still being sent.

In Pabbly Connect, each step in a workflow operates independently:

• Why the overall task appears successful: Steps 1, 2, 3, 5, and 6 (such as creating the document, sharing the file, sending the Gmail message, etc.) are completing without issues, which is why your emails and attached documents are still reaching their destinations.

• Why you receive the error email: Step 4 (Google Drive: Upload a File - Legacy) fails specifically due to an outdated connection error (400 Bad Request). Whenever any single step fails or encounters an API error during execution, Pabbly Connect marks the task status as Partial Failed and immediately sends an error notification email to alert you.

Because this individual step is failing on every run, it triggers the error email even though the surrounding steps carry on and finish.

Replacing Step 4 (Google Drive) with the standard non-legacy Upload a File action and connecting it freshly will resolve this specific step failure, resulting in a 100% successful execution without generating error emails.

Please let us know if you need any assistance updating that step!