Hi RobertoPastorino, In a case like this where a CU is identified as causing issues by Palo Alto Networks, the CU gets rolled back and then replaced. The endpoints that are delayed will never receive the "bad" CU, they will just get the next CU after the delay period ends. For example: Hour 0: New CU released, agents with out delay get updated Hour 24: CU is identified by PANW as causing issues, CU is rolled back Hour 48: New CU is released, agents without delay get updated * 72 hours after new CU released, so hour 120 * Hour 120: New CU is installed to agents with delay These are just hypothetical numbers, issue discovery, CU rollback and replacement are always dynamic and unique to a specific issue.
... View more