Looking at the Task search parameters it looks like there is no way to do API side filtering on

Task.restriction.period.start

just on

end

aka

due-date

. We are scheduling tasks out into the future that should not be performed right now. Would the team be open to adding a new search parameter for "not before" (or something like that) that would allow searching on the restriction start date? I'm happy to do the work!

Is there a reason you are not using ExecutionPeriod?

Per the docs, that is when action starts and ends on the task Identifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). We are trying to say that a task cannot be worked on before a time. We are pre-scheduling tasks and want to filter them out of the workflow. The other option could be do use status but then that would require re-processing the tasks to change the status to ready

I see. Can you file an issue with the use case?