Unidentified script continuously updating form field

BhavinG
Tera Contributor

Hi everyone,

I've been troubleshooting an issue for the past couple of days and could use some guidance. A specific field on a form is updating continuously (approximately every minute), and I need to identify the exact script, Business Rule, or workflow responsible for this behavior.

I have already exhausted standard troubleshooting methods. The Script Tracer, system logging, and standard debugging have not helped pinpoint the source.

Has anyone encountered a similar issue or have recommendations on alternative methods to track down the root cause of these frequent updates?


BhavinG_0-1780645658987.png

 

2 REPLIES 2

GlideFather
Tera Patron

ahoy @BhavinG,

 

if it is Hardware [cmdb_ci_hardware] it can be syncronised with Asset [alm_asset] and if you update one or another side, it triggers the synchronisation. Then it might be a business rule triggered by that update over and over again.

 

Very often it is caused by using current.update() in BRs, more details Recommended practices avoiding to use current.update() in Business Rules

 

It is difficult to help you without visibility to your instance but I would start with focusing on business rules running on cmdb_ci and extended tables,,

---
Where the rules are real, you'll find me

Tanushree Maiti
Tera Patron

Hi @BhavinG ,

 

Updates occurring at consistent intervals (for example, precisely every 60 seconds) are often caused by background automation processes.

  • Go to System Scheduler > Scheduled Jobs > Scheduled Jobs. Review jobs that run roughly once per minute and inspect their scripts to determine whether they are updating the record.
  • Go to Flow Designer > Executions. Check for flows or subflows executing in the background that reference the affected your target table (alm_hardware) or may be repeatedly triggering themselves through recursive execution.
  • Navigate to System Definition > Business Rules. Filter for rules that run Async or After, and ensure there are no recursive loops triggered by current.update() without setWorkflow(false)

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti