Yes, it explains.
I would suggest to use intermediate artifacts / published files to use on the "Deploy" job to know what to do instead of trigger that from "Build" job.
(I'm calling "Build" the one that runs on mid-day and "Deploy" the one that runs at "H 21 * * 1")
So, in my suggestion the flow would be that "Deploy" job will be triggered by Jenkins base on "cron" trigger and when it runs, it will checks if there is a list of thing to deploy produced by "Build" job.
So, "Build" job will archive, let's say a JSON listing all microservices that need to be deployed. Then "Deploy" job will look for that list and if it's not empty, it will deploy all those listed microservices.
I hope that helps.
Cheers,
Gianluca.