“The submission was not found in the database” Error

Error: “The submission was not found in the database”
Code: submission-not-found

This error occurs when a submitted form or data entry cannot be found in the database. As a general catch-all, reviewing the corresponding test video often provides more valuable insights into the cause of the failure.

Troubleshooting Steps:

1. Verify Form Submission
   • Form Configuration: Ensure that the form is correctly configured and that all required fields are filled out in the test script. Check for any mandatory fields that might be missing or incorrectly filled.
   • Form Validation: Confirm that client-side and server-side validation rules are met. Ensure that there are no validation errors preventing the form from being submitted.
2. Verify the CheckView WordPress Plugin is Active
   • Installed and Active: Ensure that the CheckView WordPress plugin is installed and active, and verify it is not being blocked. If the plugin is inactive, your tests will still execute but are likely to fail, as the plugin is essential for validating successful test submissions. Additionally, an inactive plugin will not suppress recipient emails or send emails to CheckView’s test inbox for verification, potentially leading to incomplete or inaccurate test results.
3. Prevent Query String (?) Redirects
   • CheckView utilizes specialized query strings when conducting tests, such as:
     
     https://domain.com/contact/?checkview_test_id=e1a71c03-ca90-44c1-afab-84e3924326e2
     
     To ensure tests can run properly, confirm that no plugins or site settings are redirecting URLs containing query strings. You can verify this by appending a parameter, such as ?test, to any URL on your site. If configured correctly, this should either load the same page with the appended query string or return a 404 error, not redirect to another page or remove the query string. Improper handling of query strings can interfere with CheckView’s ability to test forms and other site functionalities effectively.
4. Check Database Connection
   • Database Status: Verify that the database server is running and accessible. Check for any connection issues that might prevent data from being saved.
   • Database Logs: Review the database logs for any errors or issues during the submission process. Look for any failed queries or other indications of problems.
5. Review WordPress Settings
   • Form Plugins: Ensure that the form plugin or custom form handler is correctly configured and updated. Check for any settings that might affect form submission and data storage.
   • Submission Handling: Verify that the form submission handling logic is working as expected. Check for any errors in the code that might prevent data from being saved to the database.
6. Inspect Server-Side Issues
   • Server Logs: Check the server logs for any errors that might occur during form submission. Look for PHP errors, server misconfigurations, or other issues that might affect data saving.
   • Form Processing Scripts: Ensure that any scripts responsible for processing the form submission are running correctly and without errors.
7. Check for Additional Form Validation
   • Custom Validations: Review any custom validation rules that might prevent the form from being submitted. Ensure that these rules are correctly implemented and not overly restrictive.
   • Third-Party Interference: Check if any third-party plugins or scripts are interfering with the form submission process. Disable them temporarily to see if the issue is resolved.
8. Test Environment Consistency
   • Environment Match: Ensure that the test environment mirrors the production environment as closely as possible. Differences in configurations or data can affect the form submission process.
   • Data Consistency: Make sure that the data used in the test environment is consistent and reflective of real-world usage. Inconsistent data can lead to unexpected behavior in form submissions.

Additional Tips:

• Wait for Submission Confirmation: Adjust the test script in Checkview.io to wait for a confirmation message or redirection after form submission.
• Robust Selectors: Use robust selectors that accurately target form fields and submission buttons. Avoid overly generic selectors that might fail to interact with the correct elements.
• Debugging with Developer Tools: Use the browser’s developer tools to inspect the form and understand why the submission is not being saved. This can help identify issues with validation or server-side processing.
• Professional Help: If issues persist, consider consulting with a web development expert or a testing specialist for a thorough analysis and tailored solutions.