Total Field: "Submitted value ($XX.79) does not match expected value ($XX.78)

Get Help
, , , ,
1

Hello Gravity Community,

I have an odd issue that just arose after the last update.

The Total Field throws up the following error message…
"Submitted value ($XX.79) does not match expected value ($XX.78).

It is always out by 1c … If I add a 1c discount or credit to the form it simply raises or lowers the above varienience error by 1c.

I ran Logging and got the following below: Any ideas, anyone?

Thanks in advance.

Form @ Complete our booking request form to get an instant estimate - DRIVEU Sunshine Coast

2024-08-13 12:47:33.264550 - DEBUG → GFFormDisplay::validate(): Starting for form #75.
2024-08-13 12:47:33.264594 - DEBUG → GFFormDisplay::validate(): Executing functions hooked to gform_pre_validation.
2024-08-13 12:47:33.275285 - DEBUG → GFFormDisplay::validate(): Completed gform_pre_validation.
2024-08-13 12:47:33.275372 - DEBUG → GFFormDisplay::validate(): Checking restrictions.
2024-08-13 12:47:33.275855 - DEBUG → GFFormDisplay::validate(): Completed restrictions. Starting field validation.
2024-08-13 12:47:33.276187 - DEBUG → GFFormDisplay::validate(): Field validation completed in 0.000279 seconds.
2024-08-13 12:47:33.276242 - DEBUG → GFFormDisplay::validate(): Executing functions hooked to gform_validation.
2024-08-13 12:47:33.311072 - DEBUG → GFFormsModel::create_lead(): Draft entry created for form (#75) in 0.034747 seconds.
2024-08-13 12:47:33.396997 - DEBUG → GFFormDisplay::validate(): Completed gform_validation.
2024-08-13 12:47:33.397042 - DEBUG → GFFormDisplay::process_form(): After validation. Is submission valid? Yes.
2024-08-13 12:47:33.397085 - DEBUG → GFFormDisplay::process_form(): Processing completed in 0.149051 seconds.
2024-08-13 12:48:11.393157 - DEBUG → GFFormDisplay::process_form(): Starting to process form (#75) submission.
2024-08-13 12:48:11.396538 - DEBUG → GFFormDisplay::process_form(): Executing functions hooked to gform_pre_process.
2024-08-13 12:48:11.408597 - DEBUG → GFFormDisplay::process_form(): Completed gform_pre_process.
2024-08-13 12:48:11.408840 - DEBUG → GFFormDisplay::process_form(): Source page number: 4. Target page number: 5.
2024-08-13 12:48:11.408879 - DEBUG → GFFormDisplay::validate(): Starting for form #75.
2024-08-13 12:48:11.408925 - DEBUG → GFFormDisplay::validate(): Executing functions hooked to gform_pre_validation.
2024-08-13 12:48:11.417567 - DEBUG → GFFormDisplay::validate(): Completed gform_pre_validation.
2024-08-13 12:48:11.417618 - DEBUG → GFFormDisplay::validate(): Checking restrictions.
2024-08-13 12:48:11.417877 - DEBUG → GFFormDisplay::validate(): Completed restrictions. Starting field validation.
2024-08-13 12:48:11.467055 - DEBUG → GFFormsModel::create_lead(): Draft entry created for form (#75) in 0.034098 seconds.
2024-08-13 12:48:11.478756 - DEBUG → GF_Field_Total::validate(): Amount mismatch (Total Estimate - #192). Submitted: ‘$ 659.79’. Clean (int): 65979. Expected (int): 65978.
2024-08-13 12:48:11.479094 - DEBUG → GFFormDisplay::validate(): Field validation completed in 0.061174 seconds.
2024-08-13 12:48:11.479137 - DEBUG → GFFormDisplay::validate(): Executing functions hooked to gform_validation.
2024-08-13 12:48:11.582165 - ERROR → form #75: validate() - failed: Total Estimate (192 - total) - message: Submitted value ($ 659.79) does not match expected value ($ 659.78).
2024-08-13 12:48:11.582222 - DEBUG → GFFormDisplay::validate(): Completed gform_validation.
2024-08-13 12:48:11.582257 - DEBUG → GFFormDisplay::process_form(): After validation. Is submission valid? No.
2024-08-13 12:48:11.582297 - DEBUG → GFFormDisplay::process_form(): Processing completed in 0.189375 seconds.

2

Hi,

Gravity Forms recalculates the form totals on the backend, when the form is submitted, and when the total on the frontend doesn’t match the total on the backend, it throws such errors. To know exactly why the totals on your form are not matching, we’ll need to take a look at how the form is set up and run some tests with it.

If you have an active Gravity Perks subscription, you can get in touch with us via our support form with an export of the form, so we can look into this further.

Best,

1 Like