Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Not possible to prevent duplicate UI Action insert submissions (PRB1077509 - unique key violations and duplicate task numbers) without preventing legitimate subsequent inserts - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Not possible to prevent duplicate UI Action insert submissions (PRB1077509 - unique key violations and duplicate task numbers) without preventing legitimate subsequent inserts
KB0711945

Not possible to prevent duplicate UI Action insert submissions (PRB1077509 - unique key violations and duplicate task numbers) without preventing legitimate subsequent inserts


2166 Views Last updated : Aug 21, 2024 public Copy Permalink
KB Summary by Now Assist

Description

It is not possible to prevent duplicate UI Action insert submissions without preventing legitimate subsequent task creations.
 
There was a previous partial fix in Kingston and late Jakarta, where the UI Actions handling code had been amended to trace the las action performed and attempt to inhibit repeated submissions.
Ref.:
PRB1077509/KB0711941 - Multiple Submit UI Actions are possible for new task records resulting in unique key violations and duplicate task numbers
 
 

Steps to Reproduce

 

This issue is not constantly reproducible, and depends on the network latency affecting the user client session.

When the user clicks on 'Submit' or 'Create New', the request would POST and the UI Action would get disabled.

While the new record is being inserted, after a period of network latency affecting the client, the button would get re-enabled.

If the user clicks on it again thinking the previous insert has not initiated, this would trigger the exact same POST as before, trying to create the new record with same number and sys_ID, violating the unique key indexes.
 

Workaround

This problem is under investigation and targeted to be fixed in a future release. You can Subscribe to this article to receive notifications when more information will become available.
 
 

Related Problem: PRB1265879

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.