...
Common Problems
Doc Post Failure
If the a submission doesn't reach the Database Connector or when certain database operations fail, will
- Flag the submission with an error in the Submissions Table
- Send Doc Post Failure notification email(s) reporting information about the error to all tenant administrators or flow admins (if configured)
...
Example 1:
The email reports a Connection refused error - To resolve, verify the URL to your database connector is correct in business rules or Doc URI's<< Add a screen image of the Submissions UI with error icon and on-hover >>
Emails with information about the failure will be sent when certain database operations fail.
Example 2:
All DBC SQL operations are performed within a database transaction. the The following SQL errors cause the transaction to be rolled backto generate Doc Action Failure emails to tenant or flow admin users and tag the submission :
- An update statement updates ) rows and autocreate is false
- A query with autocreate=true is missing a create statement
- A query when autodelete is true and is missing the delete statement
- A query with the Delete statement and the delete Key is not defined
- A delete statement where the specified delete key cannot be found in the retreived retrieved resultset
- Browsing the URL to generate the schema for querysets
- Updates do not trigger errors due to several valid use cases for update failures ex: autocreate=true
- When calling a queryset If any one of the SQL operations (except Update) fails - For example: When calling a querySet with 1 or more autocreate or autodelete=true, iternally internally the DBC is likely to execute multiple SQL statements - it :
- It will try to delete all rows that were deleted from the form resultset that were originally in the resultset
- retrieved from the database.
- It will try to update rows from the form resultset - and if autocreate is true and the update fails, it will execute an insert for each update
- failure.
- Browsing the URL to generate the schema for querysets
Updates do not trigger errors due to several valid use cases for update failures ex: autocreate=true
tenant
Live Forms tomcat running on non-default port
...