Skip to main content
Skip table of contents

Form Builder – Error Log

The Error Log helps Form Builder users troubleshoot failed form submissions when testing newly created/edited forms, or after receiving a customer inquiry. Users are able to view the full API response in the Error Log after receiving an error upon form submission. This is great for troubleshooting issues that need a bit more investigating.

image-20240520-184202.png

To use the error log, you will need to select the date of when the form submission took place that you are investigating. The best way to find the submission you’re looking for is having the exact date and time to narrow your search.

image-20240520-184209.png

You can also use the Text search to search for specific information about the submission, like email or customer ID. Or use the Form drop down to search for only errors coming from a specific form. NOTE: not all API responses will include customer info or the form so these search tools (text search and form drop down) may not always display all error submissions. Again, the best way to narrow down your search is by having the exact date and time of the form submission.

image-20240520-184218.png

After you choose the Transaction Date (and any other filters), a list of errors will appear. To view the error, click on one of the rows. There will be 3 tabs; Omeda Response, HPCI Response, Payment Processor.

  • Omeda Response: This will be the error response from the Omeda API.

  • HPCI Response: If there was payment on the transaction that errored, you may be able to find out more info on why the payment failed using this tab which is the API response from HPCI.

  • Payment Processor: This is the API response from the actual Payment Processor so this can also provide helpful information if a payment transaction failed.

image-20240520-184225.png

Table of Contents

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.