Beginning with the Xanadu release, cyclic dependencies in recovery tasks can be avoided to prevent repeated invocation of the same plan from other plans.

For example, in the Recovery task of Cyclic plan example 1 invokes Cyclic plan example 2, Cyclic plan example 2 invokes Cyclic plan example 3 and then again Cyclic plan example 3 invokes Cyclic plan example 1. If you attempt to add a link bet Cyclic plan example 2 and Cyclic plan example 3, it is not allowed. An error message, similar to the one shown in the example, prompts the user to choose a different related plan to prevent such issues from occurring in an event.

Similarly, if plans are activated beyond 10 levels or hierarchical links involving more than 10 levels of plans are created, the following error message is displayed, suggesting the removal of the plan before saving the record.

Starting from version 6.1.x of the Business Continuity Management application, the integration of recovery task automation into the business continuity planning process is introduced. This automation aims to enhance efficiency, save time, and minimize the risk of human errors. Users who have the necessary access to the recovery task can classify it as either manual or automated. These tasks are typically organized in a sequential manner with dependencies.

To automate a recovery task, administrators or application developers create an automation flow and associate it with the task. When the task moves to the Open state (when the plan is activated as part of an exercise or an actual event), the automated flow is triggered. However, there may be instances where the automated flow fails due to system errors. In such cases, the user with access to the recovery task can activate the manual task as a backup and assign it to a designated backup assignee. The backup assignee receives a system-generated email to complete the task flow. Plan users have the opportunity to practice business continuity plan exercises and make improvements based on the obtained results.