Here are some common statuses for Backup and Sync plan executions,

Status Code	Description
WAITING_FOR_PRE_VALIDATION	The plan was entered into the execution queue, it was not yet validated or checked, and eventually may not get executed
BACKUPS_ARE_DISABLED	The plan will not execute - all backups were disabled (see Configurable Parameters and Settings)
SYNCS_ARE_DISABLED	The plan will not execute - all syncs were disabled (see Configurable Parameters and Settings)
PREPROCESS_EXECUTION_SKIPPED_BECAUSE_A_DAY_PASSED	The plan was waiting in the queue for a day or more and will be canceled, no tasks were executed yet.
PRE_VALIDATION_QUIESCE_TIMEOUT_SYSPARM_TOO_SHORT	The plan will not execute - the configured quiesce parameter (see Configurable Parameters and Settings) is shorter than 60 seconds
PRE_VALIDATION_OUT_OF_MAINTENANCE_WINDOW	The plan will not execute - the current time is not within the maintenance window (see Maintenance Concepts for more information about the maintenance window), the maintenance window is checked for all execution types - schedules, ad-hoc via the UI and via the REST API
PRE_VALIDATION_INVALID_TIMEFRAME_FORMAT	The plan will not execute - the maintenance window defined in system parameters is in an invalid format, the format should be HH:MM (see Configurable Parameters and Settings)
PRE_VALIDATION_STORE_IS_NOT_MOUNTED	The plan will not execute - for backup plans - the backup destination must be a mounted remote filesystem , you cannot backup to the local filesystem created during DPOD installation (see Configurable Parameters and Settings on how to change the destination)
PRE_VALIDATION_BACKUP_STORE_OUT_OF_SPACE	The plan will not execute - there is not enough space in the backup destination path (DPOD checks the free space percent on the mounted path, see Configurable Parameters and Settings on how to change the threshold)
PRE_VALIDATION_BACKUP_STORE_PATH_NOT_FOUND	The plan will not execute - the backup destination path was not found (see Configurable Parameters and Settings on how to change the destination)
PRE_VALIDATION_CHECK_IF_STORE_MOUNTED_SCRIPT_EXCEPTION PRE_VALIDATION_BACKUP_STORE_SPACE_CHECK_EXCEPTION PRE_VALIDATIONS_EXCEPTION	The plan will not execute - Internal exception occurred, see the accompanying error message for more details
NO_TASKS_CREATED	The plan will not execute - no tasks created, this can happen, if no devices or domains were matching the pattern in the activity, or if no devices were available. for example, the backup activity specified Device QA1 and domain Bank*, but no such domains exist on device QA1.
NO_ELIGIBLE_TASKS	The plan will not execute - some tasks were created, but all of them were skipped or failed validations. For example, secure backup task for a device that was not in DR mode
PRE_VALIDATIONS_STARTED STARTED_DIVIDING_TO_TASKS TASKS_VALIDATIONS_STARTED TASKS_VALIDATIONS_FINISHED	Interim statuses - only used as progress indication, the plan will usually not stay in this status for more than a few minutes.
READY_FOR_EXECUTION	Interim status - the plan passed all validation and has some tasks waiting for execution, it is queued and will be executed in the next minute, or is waiting for other plans to finish executing first.
PRE_PLAN_SCRIPT_STARTED	Interim status - the plan is waiting for the pre-plan script to finish execute
PRE_PLAN_SCRIPT_FAILED	The plan will not execute - the pre-plan script returned with a return code greater than 0
EXECUTING	Interim status - one or more tasks started executing
POST_PLAN_SCRIPT_STARTED	Interim status - the plan is waiting for the post-plan script to finish execute
POST_PLAN_SCRIPT_FAILED	The plan finished executing, but the post-plan script returned with a return code greater than 0
SUCCESS_WITH_SKIPPED_TASKS	All tasks either finished successfully one or more tasks skipped (for example, because the device was not available)
SUCCESS	All tasks finished successfully
FAILED	One or more tasks failed

Browser not supported