Failed Browser Step logs and notification is +1 of actual failed step

**Describe the bug** When a browser step fails, the failed step number reported to the user is +1 of the actual failed step. If step 2 fails, UI reports that step 3 failed. I exported the config to confirm this. Docker container logs also give an error of missing step during time of error. In my case, Step 2 does not find the element and continues to try for 10 seconds (hard coded static timeout). This pushes the browser outside of the default 30 second timeout session and errors. "browser_steps": [ { "operation": "Click element if exists", "selector": "button#gdpr-banner-accept", "optional_value": "" }, { "operation": "Click element if exists", "selector": "#site-signin > div > div > a", "optional_value": "" } ], "browser_steps_last_error_step": 3, "conditions": [ { "field": "None", "operator": "None", "value": "" } ], **Version** v0.55.7 **How did you install?** Docker **To Reproduce** Steps to reproduce the behavior: 1. Create a new watch 2. Add 2 browser steps 3. Have step 2 fail 4. See error, step 3 failed 5. Browser Steps UI also shows red board around empty step 3 **Expected behavior** Browser Steps that fail on step X should report step X failed, not step x +1 **Screenshots** <img width="343" height="394" alt="Image" src="https://github.com/user-attachments/assets/1b278565-5abb-4c16-9b7f-f23f71709364" /> **Desktop (please complete the following information):** - OS: CachyOS - Browser Firefox - Version 151.0.2 **Additional context** I tried a new watch I tried restarting the container I tried cloning the watch and editing I tried adding in a delay step, increasing the real step count to 3 - and error would show step 4 failed (session timeout)