I would probably approach this by defining a calender on the Orchestrator tenant and then setting up a time based trigger with that.
You can define a calender by logging in to the Orchestrator → Tenant → Settings → Non-Working days.
Every date you select there will prevent the trigger from running, so just leave out the dates you need.
You could also try to set up a custom cron expression, if the use case allows for it, but that is a little bit more complex.
Thanks for your reply.
Yes, a Non-working calendar could probably work. However, as we are talking about 2 days per month - it’s not the optimal as we then would have to mark all other days as non-working.
The best would be if there was an option to have a Working Calendar - or just be able to select the specific days per month that a process should execute on as a Trigger.
How would it work with a cron expression? Can the requirement we have be setup using that (as all dates or non-recurring per month).