A standard form confirmation can appear during a workflow step save. Check stored values and history before submitting the same action again.
Quick answer
Gravity Flow 3.1.1 addresses standard form confirmations appearing after AJAX saves on entry-detail pages with editable fields, including Gravity Perks Nested Forms. Verify that your case matches that context, update on staging, and compare the visible message with the saved parent entry, nested entry, and workflow history. Do not assume the wrong message means the save failed.
Identify the action the user took
Ask whether the user clicked Save Progress, completed a User Input step, saved a nested child entry, or submitted a new public form. Record the page and button label. These actions can share similar JavaScript components while representing different workflow transitions. A generic thank-you confirmation may make an incomplete approval look finished to the user.
Before clicking again, open the entry through a separate request and inspect its values and current step. If the first request saved successfully, resubmitting may create extra notifications or repeat custom integrations. Preserve the time and a redacted screenshot of the misleading message. The immediate goal is to tell the user what happened without creating a second action.
Build a minimal nested-entry reproduction
Use a staging workflow containing one editable parent value and one nested form with a simple text field. Record the parent and child identifiers and enter visibly different synthetic markers in both. Save the child, then use the exact parent step action from the report. Avoid real customer data and route test email to an approved internal address.
Run a control without the nested field, then restore it and repeat. If only the nested case produces the standard confirmation, you have a useful isolation result. Keep other settings stable while updating Gravity Flow. Record the installed Nested Forms, Gravity Forms, theme, and browser versions so the comparison can be repeated by support.
Illustrative diagnostic worksheet. Values are examples, not measurements from a customer site.
Read the response without confusing transport and outcome
In browser developer tools, preserve the request list for the save. Record the endpoint, response status, completion time, and the part of the response used for the visible message. Redact nonces, cookies, and submission data before sharing. HTTP 200 means the request was handled, not that the right workflow transition occurred.
Inspect stored parent values and the linked child record from a fresh view. Compare the current step, assignee, completion state, and history entry with what the user requested. Save Progress should retain the documented in-progress state; completing a step should follow its configured route. Check notification or integration logs if your workflow triggers side effects on save.
Verify the corrected interface under real conditions
After updating, repeat the exact test and confirm that the visible result belongs to the workflow operation. Test validation failure as well as success: a missing required value must remain actionable, retain the appropriate entered data, and avoid a misleading completion notice. Also test a slow network so the button and progress state do not invite repeated clicks.
Use the browser and role reported by the affected user. Admin permissions can conceal access errors. Confirm that focus and the visible message make sense after the AJAX update and that the nested field remains usable on a narrow screen. When testing duplicate clicks, keep all external destinations in test mode and verify the stored history, not just the number of visible alerts.
Recover entries reported during the incident
Create a small reconciliation list with the entry identifier, reported time, intended action, stored state, and remaining work. Contact the workflow owner through the established operational process when an entry is ambiguous. Avoid resetting every entry to the beginning: earlier approvals and integrations may be valid. Close each case when stored values, step state, and the next responsible person agree.
Working example
Use this as a read-only starting point or an evidence worksheet. Replace example identifiers with the approved staging fixture.
step_save_trace:
parent_entry: synthetic-A
nested_entry: synthetic-B
action: save_progress
expected_step: still_in_progress
expected_message: workflow_save_result
stored_values: verify_in_fresh_request
Before closing the work
- The intended step message appears.
- Parent and nested values remain linked.
- Saving progress does not finish the step.
- A repeated click does not duplicate side effects.
For help applying these checks to a live site, HandL WP WordPress support can review the affected configuration and verify the result. Continue with Gravity Flow Save Progress validation fix when that adjacent issue matches your evidence.
Helpful references