@bullj1 When a system outage occurs in Pega, any inflight cases that were mid-processing might get interrupted. If the case was in a transactional process (like a database commit), the system usually rolls back the transaction to its last successful state to maintain data integrity. However, the case is not automatically retried or resubmitted once the system comes back online. Instead, such cases may be left in an inconsistent state (e.g., stuck assignments, broken queues). Administrator intervention is required to review and resolve these cases, usually by checking queue processors, broken items, or logs.