Are there any scheduled jobs or anything that would make Request (sc_request) records inactive?

[CompleteNoobHea]

We found that the state of Approval records related to Request records are being changed from requested to not_required and we thought that this may be due to the Request records being changed by the system to inactive for some reason. Upon further investigation, we have found that multiple records are affected all within a span less than a second. 

There were no changes in the associated Request Item (sc_req_item) records that would've triggered the change on the Request records so I guess that rules out business rules here. 

Is there any reason why the system would make multiple Request records inactive? Is it doing it through a Scheduled Job or Scheduled Flow? I have already checked both and couldn't find anything. 

[Tanushree Maiti]

Hi @CompleteNoobHea 

Definitely Active is getting false , but you need to check your configuration at what scenarios it is happening .

Any rollback of Flow/workflow ,your team performed..?

[CompleteNoobHea]

Hi @Tanushree Maiti 

I have already checked through our configuration and could not find anything that’s why I was looking at the possibility that this may be OOTB. 

Also, I would like to add that when the Request record is updated after it has become inactive, it changes back to active.