To add further

We need clarification on the following:
If the system logic is designed to create an Availability line when a Priority is defined, please confirm and explain the business rationale behind this functionality.

Expected Behavior (if such a connection exists but yet to confirm):

When saving a Priority, the application should first check if an Availability line already exists.

If it does, the Priority should be saved without error, and no duplicate Availability line should be created. No errors should be triggered in this case.

If no Availability line exists, the system should automatically create one and continue saving the Priority without error.
An informational message (e.g., “Availability line created automatically”) would be acceptable.

Issue:
The current error causes significant disruption, as Priority is widely used across tasks to manage workflow. Requiring users to manually delete and re-enter Availability lines in order to set a Priority is not practical.

Note:
Since Availability is sourced from the customer location linked to the task—and is used by PSO for scheduling—there should be no functional conflict between Availability and Priority.

​@KAMANUK - this looks like a defect. Please raise a support case for it.

Already done. This happen when we update other fields as well :)