Let's say you have an Airtable form that works perfectly for you, but someone else tries to submit it and gets this message:
Refresh page to submit form
Naturally, the first thing you try is refreshing the page.
That doesn't work.
You might also try clearing the browser cache, opening the form in incognito, signing out and back in, or trying another browser.
Before spending too much time troubleshooting the browser, I would check the form itself.
Airtable currently documents two common causes for this error: the permissions on the form and an invalid condition on one of your conditional fields.

Check who can access the form
This is the first thing I would check.
Open the form's sharing settings and look at who is allowed to submit it.
If the form is set to Only users with base access, Airtable only allows Owners, Creators, and Editors to submit the form.
This is where it gets confusing.
Someone might already have access to your base as a Commenter or Read-only collaborator, so you assume they should also be able to submit the form.
They can't.
When they try, Airtable can show the Refresh page to submit form error instead of giving them a clear permissions message.
If you don't actually need to restrict the form to people with base access, I would change the sharing setting to Anyone on the web.
Then test the form again with the person who was having the problem.
There is one more setting I would check here.
If See who submitted a response is enabled, Airtable requires the person submitting the form to sign into an Airtable account.
If you don't need to track exactly who submitted each response, you can turn that setting off and allow people to submit without signing in.
If you do need to restrict submissions, Airtable also gives you options such as limiting the form to people in your organization or to a specific email domain, depending on your plan.
Check your conditional fields
If the permissions look fine, I would check any conditional fields on the form next.
Let's say you created a condition that shows a field only when another field has a particular value.
Later, someone deletes the field used in that condition or changes something about the underlying field.
You can end up with an invalid condition still sitting on the form.
Airtable lists this as another reason you can get the Refresh page to submit form error.
Go through the fields on your form that use conditional visibility and check their conditions.
If you see an Invalid condition warning, either fix the condition or remove it.
I would check every conditional field rather than stopping after finding the first one. You could have more than one broken condition on the same form.
Once you have fixed them, publish the form again and test it.
What I would check first
If the form works for you but not for another Airtable user, I would start with permissions.
Check whether the form is restricted to Only users with base access and whether the person having the problem is a Commenter or Read-only collaborator.
If the form is already accessible to the right people, go through your conditional fields and look for invalid conditions.
Those are the two causes Airtable currently documents for this particular error.
If neither fixes the problem, I would contact Airtable support rather than continuing to change random settings on the form.
If you keep running into limitations with Airtable forms, another option I normally look at is Fillout. It connects directly to Airtable and gives you more control over forms, particularly when people need to update existing Airtable records rather than only create new ones.