| AppScripts get a "Failed to establish a database connection. Check connection string, username and password."
|
July 7, 2021
04:00am PDT |
Resolved
Problem mitigated, error rates went back to normal.
|
July 5, 2021
06:30am PDT |
Problem started
Users started seeing the error message "Failed to establish a database connection. Check connection string, username and password." for JDBC connections in Apps Script.
|
|
| Apps Script returns: "TypeError: e.postData.getDataAsString is not a function"
|
June 9, 2021
09:50pm PDT |
Resolved
The issue has been resolved.
|
June 9, 2021
08:48pm PDT |
In progress
Root cause has been identified and fix is on going.
|
June 8, 2021
08:47pm PDT |
Problem started
Users started seeing the error message e.postData.getDataAsString is not a function.
|
|
| INTERNAL error for triggers
|
April 21, 2021
07:34am PDT |
Resolved
Necessary preventative measures have been implemented to avoid recurrence of this issue.
|
April 20, 2021
17:10pm PDT |
In progress
Problem mitigated again, error rates went back to normal.
|
April 19, 2021
21:20pm PDT |
In progress
A repeat of the incident occurred, since preventative measures were not yet in place.
|
April 07, 2021
22:46pm PDT |
In progress
Problem mitigated, error rates went back to normal. Work on preventative measures began.
|
April 07, 2021
06:46am PDT |
Problem started
Users started seeing the error message "INTERNAL" frequently on some of their Apps Script triggers, which caused the scripts to fail.
|
|
| Properties service returns "Data storage error"
|
October 24, 2019
3:35pm PDT |
Resolved
User property data restored.
|
October 23, 2019
06:21pm PDT |
In progress
User property writes have been restored.
|
October 23, 2019
11:10am PDT |
In progress
Root cause has been identified and fix is on going.
|
October 20, 2019
11:54pm PDT |
Problem started
User property writes began throwing storage errors, and user
property reads began returning empty data.
|
|
| Trigger event missing data
|
January 8th
1:00pm PDT |
Resolved
Authorization for the missing Google OAuth scopes is now
requested during trigger creation.
|
November 8, 2018
8:59pm PDT |
In progress
Root cause has been identified and fix is on going. A temporary
workaround is provided and can be found in the issue tracker.
|
November 4, 2018
8:25pm PDT |
Problem started
Creating Spreadsheet, Form and Document triggers via the New G
Suite Developer Hub fails to automatically request the
corresponding Google OAuth scope from the user in some special
cases, which leads to the unavailability of certain data in the
trigger event.
|
|
| OAuth popup shows error 500
|
August 7, 2018
9:57pm PDT |
Resolved
A misconfiguration was found in the OAuth system, and has been rolled back.
|
August 7, 2018
5:38pm PDT |
Problem started
For 2% of users, the OAuth prompt is showing a error 500.
|
|
| ScriptApp Trigger Outage
|
July 23, 2018
1:00pm PDT |
Resolved
Fetching triggers now working. All affected projects should now
be able to fetch triggers.
|
July 19, 2018
7:32am PDT |
In progress
Users report failures in ScriptApp when using getProjectTriggers
and getUserTriggers.
|
|
| Cloud outage 18003
|
May 22, 2018
1:00pm PDT |
Resolved
Creating Cloud Platform projects is working. Apps Scripts
created during the outage should fix themselves on the next
execution or save.
|
May 22, 2018
8:48am PDT |
In progress
Creating new Apps Script projects fails to create the associated
Cloud Platform project. You can run existing scripts, and
create and edit new scripts, but running new scripts fails
with the error
"Server error occurred. Please try saving the project again".
|
|
| 79574626
|
May 18, 2018
9:15am PST |
Resolved
Functionality for developers to view, modify and create Apps
Scripts associated with Google Sites Classic has been restored.
|
May 10, 2018
8:41pm PST |
In progress
Developers are currently unable to view or modify Apps Scripts
associated with Google Sites Classic. The list of scripts
associated with a site shows "No scripts found". New
scripts created in Sites Classic are not properly associated
with the intended site; a standalone script is created
instead. The experience for end-users viewing Classic Sites with
Apps Scripts installed is not affected.
|
|
| --- |
May 3, 2018
3:30pm PST |
Resolved
The issue has been resolved.
Some script executions may not have been recorded during the
time of the outage; therefore, Apps Script dashboard 7-day
metrics for select users may be inaccurate until 3:30pm
May 10, 2018.
|
May 3, 2018
11:45am PST |
In progress
Some developers encountered errors using the Apps Script API
and when listing/editing deployments created using
"Deploy from manifest" in the IDE. Some script executions
may not have been recorded, resulting in omissions in the
execution logs and inaccuracy of metrics in the
Apps
Script dashboard.
|
|
| 77152111
|
April 1, 2018
12:00pm PST |
Resolved
The issue has been resolved.
Executions were not recorded during the time of the outage;
therefore, 7-day metrics reported in the Apps Script dashboard
and API may be inaccurate until 12:00pm April 8, 2018.
|
| March 27, 2018 |
In progress
Script executions are not being recorded and therefore are
not being displayed in the
Apps Script dashboard
or reported in
API
queries; execution and usage metrics are
also affected.
Some views in the Apps Script dashboard may show 500 errors.
|
|
| 71854238
|
| January 13, 2018 |
Resolved
The issue has been resolved.
|
| January 4, 2018 |
In progress
A small number of users are seeing intermittent hanging
interfaces and failures accessing the service including the
Apps Script IDE and running scripts.
|
|
| 70482802
|
December 11, 2017
08:43 PST |
Resolved
The issue has been resolved.
|
December 8, 2017
16:13 PST |
In progress
Sidebars and dialogs are not loading for 50% of domain
installed add-ons.
|
|
