If your logic is more customizable / complicated, then you can always write the necessary scheduling logic in a parent workflow, which is responsible for figuring out the scheduling logic, and then triggering child workflows or actions at the appropriate times.
I discussed and came up with a solution for something similar here: Long-running entity workflows with internal scheduling.