From aa1de7842a54bd1f513d71cd84c9a184070863ce Mon Sep 17 00:00:00 2001
From: Isha vyas <72408461+Ishavyas9@users.noreply.github.com>
Date: Mon, 9 Jun 2025 19:20:38 +0530
Subject: [PATCH] Merge pull request #1689 from amanchopra1905/stage

failfast updated
---
 docs/hyperexecute-failfast.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/hyperexecute-failfast.md b/docs/hyperexecute-failfast.md
index b8f129e55..eb2305b07 100644
--- a/docs/hyperexecute-failfast.md
+++ b/docs/hyperexecute-failfast.md
@@ -58,6 +58,21 @@ failFast:
     maxNumberOfTests: 2
 ```
 
+
+:::info
+To apply `failFast` at the **scenario** level instead of the default test level, set the `level: scenario` in the YAML configuration.
+
+```yaml
+failFast:
+  maxNumberOfTests: 2
+  level: scenario
+```
+:::
+
+> **NOTE :** You can specify `failFast` at either the test level or scenario level, depending on your requirements. Both configurations will work, but can lead to unexpected results, only one should be used at a time.
+
+***
+
 For a deeper understanding of the HyperExecute YAML and its versatile features, we invite you to explore our dedicated [HyperExecute YAML documentation](/support/docs/deep-dive-into-hyperexecute-yaml/) page. This resource-rich section provides valuable insights to empower your testing endeavors.
 
 ***