Facing issue with running scheduled notebooks that uses my Google drive

Google Cloud Compute Infrastructure
1

I am facing issue with running scheduled notebooks that uses my Google drive for file I/O. Where I have attached google drive using the button available which will automatically attach the drive whenever I connect to the runtime (and not using colab library code which requires me to grant permission every time). I am facing this issue only recently.

Currently I am using Colab Pro+ account.

Current Behavior
Error “Backend execution error” occurs during scheduled notebook runs, and subsequent schedules are canceled.

Expected Behavior: The notebook should execute all code blocks without errors.

Subscription type: Colab Pro+

Browser: Chrome

Any help is greatly appreciated.

Thanks!

2

It seems like there is an issue with an automation process. I heard there is a code that prevents those kinds of actions inside the authentication page. It doesn’t seem like an error about Google Drive itself.

Also, this kind of automation is not recommended, but if you want, try authentication using web crawling modules.

3


Hi @nivethithan-vel,



Welcome to Google Cloud Community!



The “Backend execution error” in Google Colab scheduled notebooks, especially when involving Google Drive I/O, is unclear and imprecise. The recent onset suggests a change either in your notebook, your Google Drive setup, or within Colab’s infrastructure. Here’s a breakdown of troubleshooting steps:

1. Check Colab Status: Visit the Google Workspace Status Dashboard (status.google.com) and specifically look for any reported issues related to Google Colaboratory or Google Drive. Outage or maintenance may be the root cause.
1. Test with a Simple Notebook: Create a new scheduled notebook with minimal code that only reads and writes a small file to your mounted Google Drive. This helps isolate if the problem is with your specific notebook’s code or a broader issue.
1. Examine the Logs: Colab Pro+ should provide more detailed logs for scheduled notebook executions than free accounts. Look for more specific error messages within the execution logs for your scheduled notebook. These logs often contain clues beyond the generic “Backend execution error.”
1. Permissions: Double-check the permissions of the Google Drive files and folders your notebook accesses. Even with the Drive mounted, insufficient permissions can cause failures. Make sure your Colab notebook service account has the necessary read/write access.
1. File Size and Complexity: Large files or complex operations on Google Drive can sometimes exceed Colab’s runtime limits or encounter temporary network issues. Try simplifying your file I/O operations and testing with smaller files.
1. Runtime Type and Version: Ensure you are using a compatible runtime type (e.g., Python 3) and that your runtime version isn’t outdated. Older runtimes might have compatibility problems.


I hope the above information is helpful.
4

@ChieKo Thanks for the update. Google Colab has upgraded PyDrive library to a newer version in the recent release. I think that solved the issue.