Hey, unfortunately it's too irregular for a cron string 😞
Currently we're just using (partitioned) ops/graphs/jobs so i might end up implementing a sort of "pilot light" pattern - where at the beginning of every graph there's an op that consults its business calendar, and returns a non-required output if it's a relevant business day, and nothing otherwise, causing the downstreams to be skipped on non-business days.
I'll have to look at the rest of our data estate before I can say we'd actually need this - I want to transition a bunch of stuff to dagster, both feet in with the assets APIs. Once I get a better look at what we've got, I might come back with an issue. Thanks for the great work!