subtle whale
netapp.ontap.na_ontap_job_schedule does not offer an option to specify a vserver. this leads to issues when trying to create/modify a job schedule on the cluster if a job schedule with the same name exists within a vserver.
https://github.com/ansible-collections/netapp.ontap/issues/230
vivid dagger
job schedules are buggy anyway, if you create a schedule with the same name as a schedule that exists on another SVM, you cannot delete the schedule if the one in the other SVM is still in use 😄
I would suggest creating job schedules only at the cluster level, or at least using unique names