Google Apps Script Autho Email
You may have received an email stating a failure of a Google Apps Script. In most cases it is due to a script (Program or application) that has not been executed (Triggered) for some time but now the authorisation to execute has expired.
The application could be a form on your website that visitors to your website used to make a booking or contact you. When the form is use and submitted by the visitor, a response email or calendar booking etc maybe processed. This process is completed by an application (program) that executes on your authority.
From time to time, these applications will require your permission to function, particularly after a long period of inactivity or changes to the application.
The reason for the script error in the email sample is "Authorisation is required" See #3. Basically, Google will only execute a script if you have given Google permission to do so by you.
This page outlines how to address the authorisation message.
Sample Email Message from Google
How to resolve
To resolve an "Authorisation" issue as indicated in the email #3, we need to open the Google Document #1 and associated script document. Then the function #2 need to be located and executed to prompt the authorisation settings to appear.
It should only take a couple of minutes to complete this task by following the instructions below.
When you sign-in to your Google Workspace account, ensure it is the owner of the application. See "To" in email for signin user.
1. Click on the file link in the email #1.
2 When the Google document opens, locate "Tools" in the menu.
3. Select "< > Script Editor". This will open up another document that contains the associated scripts.
Accessing Tools and script editor.
4. In the Script Editor, locate the Function name as stated in the Email #2 using the drop down list next to the Bug icon.
If the Function Name does not appear, it may exist on another page. Select each page in turn until the Function name appears.
Pages are shown on left panel. Sample image show only one page called "Code.gs"
Within the Script Editors - Locate Function Name and select
5. Once the Function has been located in the Drop Down List, Select the Bug Icon.
Run DEBUG to trigger the authorisation message
6. You will then be asked to review the Authorisation Permission. Select the "Review Permissions" button.
Select Review Permissions
7. Now select your Google account. If the owner of the application is not shown, select "Use Another Account" and follow the promotes to sign is as another user.
Select the owner of the application or use another account
8. A List of Google Applications will appear that the Script will use on your behalf.
9. Select "Allow".
10. Now close the Script Tab in your browser.
11. Check the spreadsheet or document for any new entries that you may need to address. Typically, the last row in the "Form Response" Sheet for a spreadsheet.