PO runs background maintenance on unity catalog managed tables you have : for optimize will be file compaction only, vaccum is 7 days by default and analyze, and it does not run zorder so if a table has e-ordered files PO will ignore them. PO schedule isn't public so you can't really pick a safe window to z-order first or after in a reliable way.

It's recommended that you go for liquid clustering with automatic liquid clustering so the PO keeps the table clustered for you and if you find that any of your workloads can benefit from Z, just disable the PO on that scope which contain the tables and run the z-order yourself.

https://learn.microsoft.com/en-us/azure/databricks/delta/clustering