Hello @DataDev
Nice idea, I haven't thought about this before, but I like the suggestion.
If I had to implement a custom schedule, there are two ways that come to mind.
Firstly, if the schedule is relatively regular, with just an occasional day missed, you could set up a schedule as normal, but then manually pause it on the days you wish to miss.

However this isn't very dynamic. Alternatively, you could :
1) Write a notebook that connects to your calendar.
2) You then want this notebook to simply finish successfully on days you want to run the job, but error on days you don't want the job to run. The exact logic depends on your run criteria/calendar entries.
3) In your pipeline, add this new notebook as your first job, with all other jobs dependant on it.
4) Set the job to run every day (or the minimum time interval you would like between runs)
To make this easier, you could try to export your calendar as a table and point the daily checker towards this instead.
This should achieve the desired result as each day the first notebook will run, check your calendar to confirm if it should proceed or not, then either finish, or error. Assuming you job dependencies are setup correctly, the other tasks will only run on days where the first notebook, successfully finishes.
If you need me to expand further on any of these points feel free to ask. Please let me know how you get on.
Regards - Pilsner