Hi All,
As part of the volume creation workflow I also create a CDOT schedule and snapshot policy.
When executed my workflow fails with this error:
Given schedule 'XYZ' already exists Location: Row '1' step 'Create schedule'.
It appears to have attempted to create the schedule, although it already exists on the target cluster (due to a previous run).
But why does it even attempt to create these elements?
In the parameters for "Create Schedule" I define my variable "vSched" using "by searching for an existing Schedule".
And I have: only "If vSched was not found" then "Fill-in attributes for vSched and execute the command" .
For my search ("Using search parameters") I am using:
By pre-defined filters
Select one schedule by its natural keys with these parameters:
The Schedule Name = NAS_SNAP_SCHED (a constant I defined)
The Cluster name or IP = vTargetCluster.name
I thought that this was the correct way to deal with the possibility of pre-existing "elements" i.e. so that the schedule and policy are only created when necessary e.g. the first time the workflow is run against a specific cluster.
Using the "Test" button shows that the search is returning no results when "consider reservation data" is not selected).
What is going wrong here? Is there something wrong with my search - should I use a different filter/finder/key? Or is something else the problem?
Thanks once again for all your support!
