Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

Automatically reopen an Incident if the same issue is reported within 7 days

anupriya887
Giga Contributor

Can we automatically reopen an Incident if the same issue is reported within 7 days of closure instead of creating a new Incident? What would be the best approach?

1 ACCEPTED SOLUTION

Bhargavi Patel
Kilo Guru

Hi @anupriya887 

Yes, this can be achieved. The best approach is to create a Before Insert Business Rule on the Incident table that checks whether a similar Incident exists for the same user within the last 7 days and is in a closed state.

If a matching Incident is found:

  • Update the existing Incident state to Reopened/In Progress.

  • Add the new details (comments/work notes) to the existing Incident.

  • Prevent the creation of a duplicate Incident using setAbortAction(true).

Alternatively, this can be implemented using Flow Designer if the logic is simple, but a Business Rule is preferred for duplicate prevention during record creation.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.

View solution in original post

4 REPLIES 4

brianlan25
Kilo Patron

You would open a new incident. I'm note sure it would be easy to determine if it is the same issue. If you have a question like this sounds like you have a bunch of problem that you need to work on thought problem management to find the root cause and put in a permanent fix.

Bhargavi Patel
Kilo Guru

Hi @anupriya887 

Yes, this can be achieved. The best approach is to create a Before Insert Business Rule on the Incident table that checks whether a similar Incident exists for the same user within the last 7 days and is in a closed state.

If a matching Incident is found:

  • Update the existing Incident state to Reopened/In Progress.

  • Add the new details (comments/work notes) to the existing Incident.

  • Prevent the creation of a duplicate Incident using setAbortAction(true).

Alternatively, this can be implemented using Flow Designer if the logic is simple, but a Business Rule is preferred for duplicate prevention during record creation.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.

Nishant8
Tera Sage

Hello @anupriya887 , In my view, there are a couple of things to take care of

1.  How will you determine which incident was originally opened for this issue? For example, will it be based on a Category and Subcategory combination, or will other fields be used?

2. If you know the answer to point 1, you can then modify your script to look for the existing incident and reopen it.

 

Regards,

Nishant

Tanushree Maiti
Tera Patron

Hi @anupriya887 

 

Out of the box, ServiceNow generally does not support reopening closed Incidents.

I recommend creating either a child Incident linked to the original parent Incident or a new Incident instead. This approach preserves the original Incident's history, maintains SLA integrity, and allows support teams to track the ongoing issue without affecting the closed record.

 

If your business has a strong requirement to reopen the original Incident, you will need to implement custom logic, such as a script or Flow, to support this behavior.

 

In one of my previous projects, the client was using ServiceNow Event Management. For specific Configuration Items (CIs), they required the associated Incident to be reopened when a new event was received. This requirement was successfully implemented using Flow Designer.

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