AppsScriptPulse

Rhino Runtime Retirement: Action Needed for Apps Script Projects

As of February 20, 2025, the Rhino runtime is deprecated. Scripts running on Rhino will continue to function until January 31, 2026, after which they will no longer execute. Please migrate your scripts to the V8 runtime before this date. Refer to Migrate scripts to the V8 runtime.

Attention Google Workspace Developers!

A recent email to Google Workspace administrators announced the upcoming retirement of the Rhino runtime for Apps Script. As also highlighted in the Apps Script release notes, all Apps Script projects still using the Rhino runtime must be migrated to the V8 runtime by January 31, 2026, to avoid execution issues.

What this means for Workspace Developers:

If you are a Workspace developer, even if you don’t have an administrator role, it’s crucial to check your Apps Script projects for Rhino runtime usage. The email to administrators included a CSV file listing affected projects, with details such as:

  • Script URL, Script ID, Last Updated: Identifies the specific script.
  • Creator Email, Owner Email: Identifies the script’s originators.
  • Incompatibility Reason: Explains why the script needs migration.
  • Execution Count: Shows how often the script is used.
  • Additional Information: Includes opt-out status, library dependencies, etc.

Suggested Actions for Developers:

  • Non-Admins: You might want to contact your Workspace administrator to find out if any of your or your colleague Apps Script projects are on the list of affected scripts and ask for guidance on the migration process.
  • Third-Party Developers: You may want to proactively reach out to your customers to inform them of the upcoming changes, offer assistance with the migration, and ensure their scripts are updated before the deadline to prevent any disruption in their services.
  • Workspace Admins: Review the CSV file to identify your affected scripts, prioritize migrating scripts with high usage first to minimize user disruption, and understand the specific issues that need to be addressed in each script.

Important Considerations:

Google provides a migration guide and support resources to assist with the transition. In particular, it is worth noting that:

  • For Apps Script web apps and Google Workspace Add-ons “[You] must create a new version of the script with the V8 adjustments. To make the V8 version available to users, you must re-publish the script with this version.”
  • When updating standalone scripts to run on the V8 runtime, “you need to provide users at least view access to the script in order for the script’s triggers to work properly.”

It’s also important to note that while the V8 runtime generally offers performance advantages, there have been some reports of specific instances where performance with JDBC connectors might not be as efficient as in the Rhino runtime.

So don’t delay, start migrating your Apps Script projects today!

Source: Google Apps Script release notes  |  Google for Developers

Leave a Reply

Your email address will not be published. Required fields are marked *