Hi,
When updating the triggers for the service’s DTR we get a pop up notifying that such action causes some bookings to go to quarantine.
I did a couple of tests and apparently no issues were detected. In this case, we are just adding a trigger to a profile instance, and the action been performed is a copy of certain values to booking properties.
Does anyone know whether I can safely rely on my previous tests or in which cases bookings will actually move to quarantine?
Kind regards,
Hi Flávio,
Yes, that’s just a warning. Changing the properties of the service definition does not impact the ongoing bookings.
That never happens.
This popup is merely intended to inform the user that the change might result in undesirable behavior.
For instance, removing nodes from the service definition can lead to incorrect references in some bookings.
Thanks! 🙂
Maybe the error message is not completely clear, it depends on the wording:
Modifying Service defintion …. would cause -> this action is going to do that
Modifying Service defintion …. might cause -> this is a possibility but not sure.
so either check if the change is going to cause a change (show first message)
or that it might influence (show the second)
Hi André,
Thank you for your reply.
Could you indicate in which cases such update could potentially move scheduled bookings to quarantine? For instance, in case the new script logic defines a different resource for a node? Does this mean that when updating the triggers the DTR script will run for scheduled bookings? (I’m trying to understand how this was designed – for future refence)