Versions Compared

Old Version 2

changes.mady.by.user Megan Ellis

Saved on

compared with

New Version Current

changes.mady.by.user Megan Ellis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:

Table of Contents

...

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 FailureTry This...
Connection Timeout
  • Check if the submission documents/data are actually present or not in Google Drive/Sheet. Sometimes, the submission goes through successfully, but frevvo does not hear back from Google in time and after a certain timeout period throws this error.
  • Resubmit (see this documentation on how to resubmit forms/workflows).

Google Sheets

Workbook or Sheet deleted/renamed

First Column header deleted/renamed 

  • Check your Google Sheet to see if the workbook, sheet or first column header was altered. This can also happen if the sheet is sorted without excluding column headers, so that the headers end up on some other row.
  • If needed, update the Doc Actions to reflect the new name.
  • Resubmit failed submissions.
Google Sheet has a column or sheet set as a Protected Range
Google Sheets has reached the limit of 5000000 cells
  • Reduce the size of your spreadsheet. A few methods are described in this blog article.
Google Sheets or Google Drive API is not enabled
Google Drive folder deleted/renamed
  • Check your Google Drive to see if the folder was altered.
  • If needed, update the Doc Actions to reflect the new folder name.
  • Resubmit failed submissions.
Google Drive folder name set by template that resolves to null
  • Check the submission to see if the control used to set the Google Drive folder name happens to be blank or invalid.
  • If possible, edit the submission to enter a value in that control, then resubmit.
  • Make that control required or troubleshoot the business rules that set it to ensure it is always filled with a valid value.
Google Drive folder name set by template that contains an apostrophe
  • Check the submission to see if the control used to set the folder name contains an apostrophe, i.e. O'Donnell
  • To ensure templates are valid, you can set a pattern on the control(s) you are using as template(s), or write a business rule to remove apostrophes in the control(s). 

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 ?

...

  1. Update to the supported version of frevvo Google Connector.
  2. Note: If you are using Live Forms frevvo Online, cloud hosted software the frevvo Google Connector is already updated.
  3. Use the form/workflow Manually Set Doc URIs wizard and do NOT use the frevvo Google Sheet wizard

...

  • Navigate to https://security.google.com/settings/security/activity?pli=1. 
  • If you are a cloud customer, select ‘YES, THAT WAS ME’ for the unknown device with IP address 54.86.85.105 - this is the ip address of the frevvo SaaS server.

  • In-house customers may see the ip address of their own server frevvo server.
Once completed, login to the Google connector wizards will work without any error.

...

"Unknown Error has Occurred" message when logging on to the Save to Google Spreadsheet wizard

In-house customers:

frevvo in-house customers may encounter an "Unknown Error has Occurred" error when logging on to the Save to Google Spreadsheet wizard. If you see "Error creating bean with name 'credentialController" in the <frevvo-home>/tomcat/logs/frevvo.log file, then the error was caused by starting  without starting frevvo without the client_secrets.json file present in the <frevvo-home>/tomcat/lib folder. Follow these steps to resolve the issue:

  1. Stop frevvo.
  2. Navigate to the Credentials screen for the project you created for your Google Account at https://console.developers.google.com. 
  3. Click the Download JSON file.
    1. Rename JSON file as client_secrets.json
    2. Copy it to tomcat/lib folder.
  4. Restart frevvo.

Cloud and in-house customers:

...

There are other causes for this error. Contact  Contact frevvo support if this solution does not solve your problem.

...

You may see the error: "Syntax Error: missing ; before statement" followed by the name of your form/workflow and the name of the rule containing the error in the debug console when testing a form/workflow that reads or updates a Google sheet via the Google Connector.

Image Removed


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 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.

Alternatively, you may add code to your rule to strip the commas:

...

.

...

Then, pass the variable "tcomma" in the updataparams rule instead of the original control value. 

Invalid String Literal

If you see the error "invalid string literal" when using a business rule to read or update a google sheet, make sure that you have commented out the slashes in your oAuth Code, as in OAuth21\/\/0dqqBnY...

...

You may encounter this error when performing read/update/write operations to a Google sheet from a form/workflow. 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 frevvo 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

...