Record Producer

[sri10120]

I have a record producer that creates an incident.

Issue: Multiple incidents are getting created for a single submission.

What are the common reasons for this behaviour?

[AndersBGS]

Hi @sri10120 ,

have you looked into the record producer script?

[keshav77]

@sri10120 have gone through the record producer script are you guys calling an array to create records  in that script

[VaishnaviK43271]

Hi @sri10120 !!

Common Reasons:

1. Multiple Submissions Triggered:

   • Users might click the submit button multiple times, especially if the page is slow to respond.

   • Lack of UI feedback (like a loading spinner) can cause repeated submissions.

2. Business Rule / Script Issue:

   • A before or after Business Rule on incident or sc_req_item may be running multiple times unintentionally.

   • Scripts in the Record Producer might create an incident multiple times instead of using current properly.

3. Workflow / Flow Designer Trigger:

   • If a workflow or flow is set to run on insert and also on update, it may create duplicate incidents.

   • Loops in the flow logic can also trigger multiple incident creations.

4. Client Script / UI Action Re-submission:

   • Client scripts or UI actions that trigger submit() programmatically may run more than once.

5. Integration / External Calls:

   • If the Record Producer triggers a REST or inbound integration, repeated callbacks can create duplicates.

Tips to Prevent Duplicates:

• Disable the submit button after the first click (UI feedback).

• Check Business Rules and scripts for multiple insertions.

• Use current.isNewRecord() or current.inserted flags in scripts to ensure a single creation.

• Test the Flow Designer logic to ensure it triggers only once per submission.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for.

Thank You