Snapmirror lag thresholds are incorrect in AIQUM

AIQUM reports alerts Mirror Replication Lag Warning every X hours
The actual SnapMirror relationship uses a larger value for the schedule than the warning
- For example:
  - Lag warning in AIQUM is coming every 2 hours
  - Lag warning threshold is set to 150%
  - The schedule is set to 2 hour interval in SnapMirrror
  - Therefore, 150% should be 3 hours
AIQUM is not calculating the warning and error threshold values correctly for SnapMirror relationships
AIQUM au.log shows:
WARN [foundation-poll-2] c.o.s.a.d.n.t.z.ZAPIConnection (ZAPIConnection.java:729) - [netappfoundation] <cluster_fqdn> - <cluster_fqdn> <cluster_fqdn> - Ignoring failed zapi: job-schedule-cron-get-iter; errno: 13115, reason: Invalid value specified for "key-0" element within "job-schedule-cron-get-iter-key-td": "<stale_cluster_uuid>"
Running job schedule show in ONTAP shows some schedules with cluster name as a stale UUID instead of the proper cluster name
> job schedule show -fields cluster,description cluster vserver name description ------------------------------------ --------- ----------------- ------------ <stale_cluster_uuid> <vserver> <schedule> <schedule_description> <stale_cluster_uuid> <vserver> <schedule> <schedule_description>
In System Manager, Protection > Overview > Local Policy Settings > Schedules
- Some of the schedules have a blank schedule
- When trying to edit these schedules it will just load forever in the GUI and will not load anything