What happens to a continuity event when it is cloned?

When a continuity event is cloned, it starts immediately, meaning that a duplicate of the event is created and initiated right away rather than maintaining the timing of the original event. This is useful in situations where rapid response is needed or when there is a requirement to have multiple instances of the same event running concurrently without having to manually adjust start times.

In contrast, the original start time of the event is not retained in the cloned instance, as the purpose of cloning often includes immediate activation. The cloning process generally allows users to quickly replicate an event without the need to go through the entire setup process again, making it efficient for event management.

While cloning allows for customization, it does not require re-entering all details unless modifications are needed for the new event set-up, making this process streamlined for managing continuity plans.