Instance Scan linter check experiences timeouts.

Jeny Devassy
Tera Contributor

Linter check, full instance scan fails due to a timeout. I'm looking for occurrences of a specific string throughout the instance. How can I address this timeout problem?
Attached below is the screenshot of the error. 

JenyDevassy_0-1709025175673.png

 

@Mark Roethof 

1 ACCEPTED SOLUTION

Mark Roethof
Tera Patron
Tera Patron

Hi there,

 

What kind of check are you using? Column Type Check or Linter Check perhaps?

 

It's not unusual for those 2 type of checks to run several minutes. Really depends on the size of your instance. For one customer of mine, Linter Checks run generally 8 minutes, while for another customer of mine, Linter Checks generally run about 20 minutes. This is just due to all script fields on all tables being checked.

 

You can increase the timeout by updating:
- Transaction Quote Rule "Scan timeout" [sysrule_quote] < this is for the whole scan
- System Property "glide.scan.process_check.time_out" [sys_properties] < this is for individual checks (note: this property does not exist out-of-the-box, you need to add it)

 

So do also take note of the System Property mentioned! The answer from Sandeep is only half the answer.

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

View solution in original post

2 REPLIES 2

Community Alums
Not applicable

Hi @Jeny Devassy ,

Set the execution time of a single scan by implementing Transaction Quota Rules. Setting of a quota rule prevents your instance from running a long scan.

Before you begin

Role required: admin

Procedure

  1. Navigate to All > System Definition > Transaction Quota Rules.
  2. To set a definite execution time, select Scan timeout.
  3. Enter the definite execution time in the Maximum Duration (seconds) field and select Update.
    Note: The minimum allowed timeout threshold is 5 seconds. If you set the timeout to anything less than 5 seconds, the system still considers it to be 5 seconds. By default, it has been set to 10,800 seconds.
    The scan fails if the execution time exceeds the set timeout. For more information on the type of scan you want to run, see Configuring Instance Scan .

Also, follow the doc :https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/health-scan/...

 

Mark Roethof
Tera Patron
Tera Patron

Hi there,

 

What kind of check are you using? Column Type Check or Linter Check perhaps?

 

It's not unusual for those 2 type of checks to run several minutes. Really depends on the size of your instance. For one customer of mine, Linter Checks run generally 8 minutes, while for another customer of mine, Linter Checks generally run about 20 minutes. This is just due to all script fields on all tables being checked.

 

You can increase the timeout by updating:
- Transaction Quote Rule "Scan timeout" [sysrule_quote] < this is for the whole scan
- System Property "glide.scan.process_check.time_out" [sys_properties] < this is for individual checks (note: this property does not exist out-of-the-box, you need to add it)

 

So do also take note of the System Property mentioned! The answer from Sandeep is only half the answer.

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn