REQ increment by one

[VL10]

Across our instance, so from main app or via a service catalog. the generated REQ always skip one.   Is this a config setting or intentional mandatory behavior?

[VL10]

When viewing that script, on our instance I see this message "Access Message - This is a high priority file type, and if altered it might generate a skipped record during the next upgrade. For more information"

I compared against a PDI and I see they are the same, so I am wondering how we could have broken this.

[Bert_c1]

There a multiple reasons for the behavior. One is creating the new record but not saving it. Default behavior is that numbers are generated when the form loads. To prevent this, see:

https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/field-admini...

And set the system property 'glide.itil.assign.number.on.insert' to true to test.

It does seem that some customization is responsible.

[VL10]

Nice one to check, had my hopes up.. but it was set to true.   I have found the date this started happening but could not find an INC or Enhancement that was related to numbering and could have introduced something wrong.   If there is a way to scan for all changes to scripts or business rules etc for a duration then maybe I can identify the customization that broke this..

[Mark Roethof]

Nice that you found a data. Can het it also be a Hot Fix or Patch that was applied at that time?

"but could not find an INC or Enhancement that was related to numbering"

I wouldn't assume its a change on purpose, though more something by accident which might not even look related. Though like if there was already a scripting mistake in the REQ area, this could be caused by this. Like in this topic was already mentioned, already when you open a REQ without saving, it would eat a number, that's not something you would immediately think of.

[Community Alums]

Maybe try running an instance scan and reviewing the results or looking at your upgrade history