ServiceNow - Zurich : Incident record suddenly disappeared and is no longer searchable by number

DanielR41508060
Giga Contributor

Hi everyone,

 

Has anyone experienced an Incident record suddenly becoming unavailable in ServiceNow while actively working on it?

 

In my case:

  • The Incident was successfully created and accessible.
  • The Incident was assigned to a Service Desk analyst.
  • Impact was set to Medium and Urgency to High (P2).
  • The last change made was updating the Category to Network and Subcategory to Firewall.
  • Immediately afterward, the Incident was no longer accessible.
  • Searching directly for the Incident number does not return the original record.

Interestingly, the search itself appears to work. Another Incident that contains the missing Incident number in its Short Description is returned, but the original Incident record itself is no longer found.

 

I also have a system-generated ServiceNow notification confirming that the missing Incident previously existed and was assigned to the Service Desk.

 

Our normal analyst workflow does not provide the ability to delete or to close an Incident, so I am trying to understand what could cause an existing Incident to apparently disappear.

 

Has anyone seen similar behavior?

 

Could this potentially be related to a Business Rule, Flow Designer flow, ACL/security rule, assignment logic, Domain Separation, or another automated process affecting record visibility?

 

I have already escalated this internally for investigation, but I am interested to know whether anyone in the community has encountered something similar.

 

Thanks!
Daniel

0 REPLIES 0