Skip to Main Content
Feature Request FR-4935
Product Area User Interface
Status OPEN

2 Voters

Silent handling for duplicate page submissions

rode.mb Public · Jun 25 2026

Idea Summary

Oracle APEX already detects duplicate page submissions when Enable duplicate page submissions = No is configured. However, the only available behavior is to reject the request with an error message and optionally provide a continuation URL.

I would like an additional option to silently ignore duplicate submissions.

This would allow APEX to discard subsequent submissions that are identified as duplicates without displaying an error to the user. The original request would continue to be processed normally, while all further duplicate requests would simply be ignored.

Use Case

Duplicate submissions are often caused by normal user behavior or browser automation rather than actual application errors. Typical examples include:

  • The user presses Enter twice in quick succession (e.g. on the login page).
  • A password manager automatically submits the login form while the user also presses Enter out of habit.
  • Multiple buttons or Dynamic Actions on the same page legitimately trigger page submits, making it difficult to disable every possible submit mechanism on the client.
  • Slow network connections cause users to click or press Enter multiple times.

In these situations, APEX correctly detects the duplicate request, but the user receives an unnecessary error message even though the application behaves correctly by preventing duplicate processing.

Developers can implement client-side JavaScript workarounds, but these cannot reliably cover every possible submit path and duplicate detection is already performed by APEX itself.

Preferred Solution

Extend the duplicate submission handling with an additional declarative option, for example:

  • Show error (current behavior)
  • Redirect to URL (current behavior)
  • Ignore duplicate submission silently

With the new option, APEX would simply discard any duplicate request after the first successful submission without displaying an error message or interrupting the user experience.

This idea is open.

Comments

Comments

  • ej egyed OP 2 weeks ago

    It looks like this may already be addressed in 26.1 based on the info in this blog post (Under the Built-in click throttling header): https://blogs.oracle.com/apex/trigger-actions-in-oracle-apex

    I'm not sure if the blog post is for all types of duplicate submissions, or just Trigger/Dynamic Actions.

  • rode.mb OP 2 weeks ago

    @ej egyed 

    Thanks for the reference. However, the built-in click throttling introduced with Trigger Actions does not address this idea.

    According to the blog post, the throttling applies specifically to Trigger Actions and blocks subsequent clicks on the same row and button until the triggered action set completes.

    The duplicate page submission setting is broader and operates at page-submit level. A page can be submitted through many different paths, for example:

    • Standard submit buttons
    • Different buttons using different request values
    • Dynamic Actions
    • JavaScript calls to apex.page.submit
    • Pressing Enter in a form field
    • Native browser form submission
    • Password managers automatically submitting a login form

    For example, a password manager may submit the login form while the user also presses Enter. There may be no Trigger Action or even a button click involved.

    Client-side throttling also cannot reliably handle submissions from different sources or separate requests that reach the server almost simultaneously.

    This idea is therefore not about preventing repeated clicks on a specific UI component. It is about changing the behavior after APEX has already detected a duplicate page submission. Instead of displaying an error, APEX should optionally ignore the duplicate request silently.