feat: add failure strategies

Signed-off-by: Animesh Pathak <[email protected]>

Author: Sonichigo

docs/database-devops/use-database-devops/failure-strategies.md

@@ -0,0 +1,76 @@
+---
+title: Failure Strategies in Database DevOps
+sidebar_label: DB DevOps Failure Strategies
+description: Learn about supported failure strategies in Harness Database DevOps, including rollback options such as Mark Changeset Ran and Ignore.
+sidebar_position: 6
+keywords:
+  - database failure strategies
+  - db rollback
+  - harness database devops
+  - failure handling
+  - changeset rollback
+  - dbops pipeline
+  - database automation
+  - database deployment failure
+  - database ci cd
+  - liquibase rollback
+tags:
+  - harness-db-devops
+  - dbops
+  - rollback
+  - failure-strategies
+---
+
+In Database DevOps pipelines, failures may occur during execution due to invalid changes, dependency conflicts, or runtime issues. Harness provides rollback-focused failure strategies to help you manage such cases.
+
+:::info
+This document focuses on failure strategies specific to Database DevOps steps. For general failure handling in Harness pipelines, see [Failure Strategies](https://developer.harness.io/docs/platform/pipelines/failure-handling/define-a-failure-strategy-on-stages-and-steps/).
+:::
+
+## Supported Failure Strategies
+
+### Mark Failed Changeset Ran
+The **Mark Failed Changeset Ran** option is available in the **Apply Schema** step under Harness Database DevOps.  
+
+When enabled, it ensures that failed changesets are marked as **ran** in the database changelog table, even if they don’t execute successfully.  
+
+- **When to use:**  
+  Use this option when you want rollback steps to include failed changesets, so that rollback scripts can attempt to clean up any partial changes. This is particularly useful for databases that implicitly commit DML statements (such as Oracle), where rollback logic must handle partial failures.  
+
+- **Outcome:**  
+  - The failed changeset is flagged as **ran**, so it won’t be retried in future runs.  
+  - If a rollback step exists (and rollback scripts are defined), it will execute rollback logic for the failed changeset.  
+
+![Apply Schema with Mark Failed Changeset Ran enabled](./static/mark-failed-changeset-ran.png)
+
+:::info
+For more details, see [Mark Failed Changeset Ran](../features/mark-failed-changeset-ran.md).
+:::
+
+### Ignore
+Skips the rollback attempt for the failed changeset.
+
+- **When to use:**  
+  If the rollback expression may not be valid due to an earlier failure (for example, if a tag before the update did not execute successfully).  
+
+- **Outcome:**  
+  The failed changeset remains as-is, and the pipeline continues execution without reverting it.  
+
+![Ignore Failure Step](./static/image.png)
+
+:::caution
+Use this strategy carefully. Ignoring a failed rollback can leave your database in a partially applied state.
+:::
+
+## Unsupported Failure Strategies
+The following strategies are **not supported** in Database DevOps steps:  
+- Retry  
+- Mark as Success  
+- Stage-level failure handling  
+
+If these are configured at higher levels, Harness ignores them during Database DevOps step execution.  
+
+## Best Practices
+- Always test rollback scripts alongside forward changes to ensure safe recovery paths.  
+- Use `Ignore` only when rollback logic is invalid or unnecessary.  
+- Prefer `Mark Failed Changeset Ran` when you want to unblock pipeline execution but avoid reapplying the same changeset.