From time to time we get the following error trying to create a booking from a custom wizard:
ResourceManagerErrorData: ErrorReason: ServiceWithSameNameAlreadyPlanned
We noticed that this can happen if there is still a service existing with the same name as the service that would be created by the booking we are trying to create. Is this the only case or are there also other cases that could throw this error (e.g. overlapping with another booking that has a service with another name)?
Hi Michiel, according to RN18279, this error is only raised when trying to save a ServiceReservationInstance or ServiceReservationDefinition that has the same name and overlapping timerange with another reservation.