Duplicate problem created post closure of P1 incident at the same time

AshwiniSawant
Tera Contributor

Hello Everyone,

 

We have identified an issue where, following the closure of a Major Incident (P1 incident), duplicate problem records are being created. One record is generated under the user's name, while another is created by the system.

This occurrence appears to be random.

AshwiniSawant_0-1747765642013.png

Also, issue is reproduceable in the the lower instance. 

 

Could anyone assist in identifying the root cause of this issue? Thank you.

1 ACCEPTED SOLUTION

@AshwiniSawant 

I shared solution for this recently here, sharing it again

Automatic problem record is getting created when M1/M2 incident getting resolved 

1) either deactivate that subflow

OR

2) Remove that Step 8, remember you will have to update the playbook in the correct scope

AnkurBawiskar_0-1747826642950.png

 

 

OR

3) Update that flow action

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

7 REPLIES 7

@AshwiniSawant 

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Hello @Ankur Bawiskar ,

 

I'm not getting option to deactivate this subflow, could you please suggest on this ?

 

AshwiniSawant_0-1747835025024.png

 

@AshwiniSawant 

did you check the other 2 options

2) Remove that Step 8, remember you will have to update the playbook in the correct scope

AnkurBawiskar_0-1747835993864.png

 

 

 

OR

3) Update that flow action in correct scope

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader