Flow execution errors

[Tony Kim]

We have some custom actions built to move computer objects to specific OUs depending on what states or substates are changed and set the description or remove from certain groups. Most of the time it seems to work fine but there are several times it fails. I noticed at the top of the execution page it says:

"Run as: ServiceNow MID server Service Account" when it completed successfully 

and

"Run as: System" when it errors

We don't have the check box checked to use the ServiceNow MID server Service Account in the credentials setup section. Does anyone know why it's running as that instead of system user that is set in the flow properties or why it's  failing sometimes as system user?

I can't find anything in the system logs and the only error I see in the execution is 

[Tony Kim · Accepted solution]

We found the issue to be the assets were not in AD when the flow ran. We had a clean up process to remove computers out of AD and SCCM whenever they were reclaimed from a user then added back when reimaged.