Audit history duplicate entry with same update number

Rada Florin-Adr
Tera Contributor

Hello everybody!
I'm having trouble identifying an instant state change on a Incident ticket.
The change doesn't happen always,just from time to time.
Also , I'm not sure how I end up in this situation : having 2 entries for the same field with same update number.
Did someone encounter this before ? If yes , where does it come from ?
A little background :
A flow changes the state using an Update Record action to Resolved.
Instantly , the state goes back to In Progress.
What I did until now : 
Used Script Tracer ( Nothing relevant as I've failed to replicate the issue)
Used Debug Business Rules ( Replicated the issue but couldn't find any BR on incident that was doing this)



2 REPLIES 2

Tony Chatfield1
Kilo Patron

Hi, running a quick test in a PDI I can replicate the issue with duplicate update numbering using current.update() in a before BR, so I would suspect you have before BR, flow etc that is calling update() method which is then followed by additional BR or flow that resets\changes the values.

Sumanth16
Kilo Patron

Hi @Rada Florin-Adr ,

 

It sounds like one BR is triggering the other - you can verify this if you do a BR debugging.

There must be .update() in business rule. If .update() is requiredb try adding .setWorkflow(false) to the the BRs to prevent this, i.e.

 

Please refer to below thread:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0691454

 

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

 

Thanks & Regards,

Sumanth Meda