On this page:
Table of Contents
...
If the submission doesn't reach the Google Connector, all tenant administrators or flow 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/flow 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/flows to my Google Account ?
...
- Update to the supported version of frevvo Google Connector.
- Note: If you are using Live Forms frevvo Online, cloud hosted software the frevvo Google Connector is already updated.
- Use the form/flow Manually Set Doc URIs wizard and do NOT use the frevvo Google Sheet wizard
...
If you use the Doc Action Wizard to Send Data to Google Sheet, your Checkbox (multi-select) controls, repeat controls, and tables will pass to the spreadsheet as a comma space separated list. However, if you are passing those values using a business rule to update the Google Sheet, you may see it populate the sheet in error, such as "[Ljava.lang.String;@43156d18". The best way to correct this is to add some standard javascript to your rule to join the array into a string, such as this:
...
This may be because you are using an invalid or revoked access token in your business rule. Make sure you are using a valid access token and retest.
This error can also occur if you are writing to a Google Sheet using a business rule, 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. This will be fixed in a future release. A workaround is to add code to your rule to strip the commas:
Code Block |
---|
//Remove Commas var t = FullName.value; var tcomma = t.replace(/,/g," "); |
Then, pass the variable "tcomma" in the updataparams rule instead of the original control value.
Internal Server Error
You may encounter this error when performing read/update/write operations to a Google sheet from a form/flow. The Google API can never be a replacement for a database in terms of reliability. There are no SLAs associated with free google accounts. makes multiple http calls to the Google API with no guaranteed SLA. As the load increases, the chances that the Google service might fail increases. If you encounter the 'internal server error', the only thing to do is to try again later
...