On this page:
...
If the submission doesn't reach the Google Connector, all tenant administrators or workflow admins (if configured) will receive a Doc Post Failure notification email reporting information about the error. Note the email subject contains the server name where the form/workflow is hosted.
Here are some examples:
There are a number of reasons why your data or documents may not post successfully to Google Sheets/Google Drive. Here are some common reasons and troubleshooting actions you can take.
Possible Reason for Doc Post Failure | Try This... |
---|---|
Connection Timeout |
|
Google Sheets Workbook or Sheet deleted/renamed First Column header deleted/renamed |
|
Google Sheet has a column or sheet set as a Protected Range |
|
Google Sheets has reached the limit of 5000000 cells |
|
Google Sheets or Google Drive API is not enabled |
|
Google Drive folder deleted/renamed |
|
Google Drive folder name set by template that resolves to null |
|
Google Drive folder name set by template that contains an apostrophe |
|
OAuth Token expired | Follow these instructions to regenerate your OAuth token. Then, update your Doc Actions and rules to reflect the new token. |
Why won't the Doc Action wizards connect forms/workflows to my Google Account ?
...
This error can also occur if you are writing to a Google Sheet using a business rule using the deprecated '&updates' parameter, and you have a text or textarea control that gets a value with a comma at runtime. For example, if you are passing a control in the var updateparams rule such as "FullName" and the runtime value entered is "Smith, John" the comma can interfere with the comma-separated update parameters being passed to the Google Sheet. To correct this, please update your business rule to use the '&updatesjson' parameter as described in this documentation.
...