The submit button gives no feedback. The useful response is a targeted correction with an observable acceptance check. That keeps the repair tied to the problem instead of turning it into an open-ended redesign.
Find the likely cause
The user cannot tell whether the request is processing.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Provide a clear processing state and confirmed outcome.
A form should request the information needed for the next step while making expectations and recovery clear.
Check that the repair worked
Test slow connections and repeated clicks.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: shortening the form increases irrelevant inquiries. Keep a small number of meaningful fit questions.
Monitor the useful outcome
Track successful submissions, field errors, inquiry quality, and device-specific completion issues.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.