Merge pull request #2081 from SanjaySingh387/stage

error handling

Author: amanchopra1905

docs/error-handling-kaneai.md

@@ -48,7 +48,7 @@ This page provides a comprehensive reference for common errors encountered when
 
 Use this guide to quickly identify, understand, and correct authoring issues to ensure your test cases run smoothly.
 
-## Error categories for Web and App Authoring 
+## Error Categories for Web and App Authoring 
 
 ### Unsupported Operation
 **Description:** This command is not supported while authoring test cases. It applies to actions that cannot be executed in the authoring environment. <br />
@@ -149,6 +149,60 @@ Use this guide to quickly identify, understand, and correct authoring issues to
 
 ---
 
+### Captcha Blocked
+
+**Description:** If CAPTCHA is detected on screen, the test flow will be halted immediately, as interacting with CAPTCHA (e.g., solving puzzles, entering characters) is not supported. <br />
+**Common Authoring Error:** Selecting CAPTCHA checkbox or entering CAPTCHA text. <br />
+**Suggested Ways:** Generally, CAPTCHA is not present in application used for testing. If you encounter a CAPTCHA, try testing the application where CAPTCHA is disabled or not triggered.
+
+---
+
+### Loop Detected
+
+**Description:** The same operation is repeated 3 or more times without any state change, indicating a possible infinite loop.<br />
+**Common Authoring Error:** Repeating the same action (e.g., clicking) without checking state.<br />
+**Suggested Ways:** Review and update the flow to ensure that each iteration results in a state change to avoid loops.
+
+---
+
+### Persistent Loader
+**Description:** If a loading spinner or progress indicator stays visible for too long—specifically, after waiting multiple times or for more than 30 seconds—it usually means the system is stuck and not progressing as expected.<br />
+**Common Authoring Error:** Waiting forever for the loader to go away without handling timeouts.<br />
+**Suggested Ways:** Implement a timeout to stop waiting after a reasonable period. Use checks that confirm when the page or content has fully loaded instead of relying only on the loader disappearing.
+
+---
+
+### Dead Click
+
+**Description:** If you keep clicking the same element but nothing happens—no change on the screen, no popup, and no response—this means the click isn’t having any effect.<br />
+**Common Authoring Error:** Repeatedly clicking on an element that isn’t interactive or is disabled.<br />
+**Suggested Ways:** Make sure the element you want to click can actually be clicked and will trigger some action before clicking it. stop the flow if clicks don’t cause any response.
+
+---
+
+### Navigation Stuck
+
+**Description:** If you try to navigate multiple times but nothing changes on the screen, and the system can’t confirm that the navigation succeeded, it means the navigation is stuck.<br />
+**Common Authoring Error:** repeatedly navigating without checking if the page or state actually changed.<br />
+**Suggested Ways:** check the navigation to ensure it is successful and the page or state changes as expected.
+
+---
+
+### Lambda Error
+
+**Description:** This error indicates an internal issue within the system. it may be caused by problems such as creating input parameters, accessing secrets, or other internal issues. <br />
+**Common Authoring Error:** Errors related to parameter configuration, secret management, or system-level issues. <br />
+**Suggested Ways:** Please attempt to resolve the issue on your side. if the problem continues, contact support at support@lambdatest.com for assistance.
+
+---
+
+### Reached Maximum Step Limit
+
+**Description:** During the generative step, if the number of steps reaches the maximum limit of 50, this error occurs.<br />
+**Common Authoring Error:** Flows that are too long or contain loops causing excessive steps.<br />
+**Suggested Ways:** Simplify the flow by breaking it into smaller parts and ensure there are no infinite loops or unnecessary steps.
+
+---
 
 <br />
 > _Have any feedback or request? Reach out to us via support@lambdatest.com and we would be happy to hear from you._