TWL-KB-032 · Power Apps · Everyday user

Form submission fails in an app

Do not press Submit repeatedly.

Applies to: Power Apps canvas apps.

Revision 5 · 18 November 2026 · General first-line guidance. Wording varies by version; a symptom is not a confirmed diagnosis.

Submit error / required field warning. Do not press Submit repeatedly.
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

What does the message mean?

Some rows describe a visible symptom rather than an exact message. Wording marked “varies” may differ on your screen.

What you seeWhat it may indicateWhat to check
Submit error / required field warningValidation, access or the data source may have stopped the save. The record may still need checking.Do not press Submit repeatedly.
No message at allProblems can happen without any message. A blank screen or a missing control is still useful evidence.Record the visible behaviour, the time and who is affected. Do not guess a code.
First checks: Protect what you entered; Read field errors; Check the existing record; Give sanitised evidence
Original explainer illustration, not a product screenshot. Select it to enlarge. All information is also in the text.

Step-by-step checks

Work in order and stop when it is resolved. If your screen differs, note what is different and ask IT or the owner.

  1. Protect what you entered

    Do this
    Keep the form open and preserve information only through an approved route.
    What you should see
    Your entries remain on screen.
    Then what?
    If this explains what you see, record it and continue only if the next check still applies.
  2. Read field errors

    Do this
    Look for a marked required or invalid field without clearing the form.
    What you should see
    A field or message is highlighted, or none.
    Then what?
    Record the result without changing settings. Stop if work, data or security could be affected.
  3. Check the existing record

    Do this
    If permitted, ask the owner whether the first attempt created or changed a record.
    What you should see
    You know whether a duplicate could result.
    Then what?
    Use only the approved action described here. If it does not match your screen, stop and ask IT.
  4. Give sanitised evidence

    Do this
    Send the exact message and the app name to the maker.
    What you should see
    The maker has what they need.
    Then what?
    If unresolved, contact IT or the owner with sanitised evidence. Do not repeat actions that could duplicate data.

When to stop and contact IT or the owner

What to put in your support request

The app and version if visible, your device, the time, the exact message, who is affected, and the checks you tried with what you saw. Remove names, addresses and confidential content from screenshots. Never send passwords or MFA codes.

Microsoft reference

Microsoft documentation for this topic (opens a new tab). Some links are product hubs. Official pages may include advanced steps; ask IT before applying them on a managed device.

Related guides

The Workflow Lab is independent of Microsoft and is not your employer’s service desk.