Have had a few cases arise where a start date was set for a new method period that started in an unlocked period that occurred prior to a locked period. Understood it isn't possible to insert a period like that in AQTS presently, but the ProvisioningTool only throws a WARN and then says the method period was set successfully when it actually wasn't. Example below, note that the method was NOT created successfully. Trying to verify if the WARN message seen is unique to this case or if it may be encountered in other cases where the method is actually set successfully (more of an issue if that warning isn't unique to failures...).
08-26 07:52:42.839 WARN - 'Dissolved oxygen.mg/L.EDL@374938122251801' is locked: Default metadata change with time range 1900-01-01T05:00:00Z/MaxInstant intersects approved region MinInstant/2025-01-16T16:55:00Z
08-26 07:52:42.969 INFO - e00681c91fc2453f80796a1f7c9c931c: 1 method(s) created successfully.
Have had a few cases arise where a start date was set for a new method period that started in an unlocked period that occurred prior to a locked period. Understood it isn't possible to insert a period like that in AQTS presently, but the ProvisioningTool only throws a WARN and then says the method period was set successfully when it actually wasn't. Example below, note that the method was NOT created successfully. Trying to verify if the WARN message seen is unique to this case or if it may be encountered in other cases where the method is actually set successfully (more of an issue if that warning isn't unique to failures...).
08-26 07:52:42.839 WARN - 'Dissolved oxygen.mg/L.EDL@374938122251801' is locked: Default metadata change with time range 1900-01-01T05:00:00Z/MaxInstant intersects approved region MinInstant/2025-01-16T16:55:00Z
08-26 07:52:42.969 INFO - e00681c91fc2453f80796a1f7c9c931c: 1 method(s) created successfully.