[Bug]: stale element not found in the current frame error displayed randomly with high frequency - element click and assertion get text

[kholoodGamal]

Describe the bug
stale element not found in the current frame error displayed randomly with high frequency with element click and assertion "get text"

Link to SHAFT_Engine Console logs
https://gist.github.com/kholoodGamal/4ede38aab0d34805527a4cde16d0cf1d

Link to SHAFT_Engine summary Report HTML
https://gist.github.com/kholoodGamal/627ccba7e8528981421adc484c43146f

Environment

1. SHAFT_Engine version that exhibits the issue (Note: We support only the latest release): 8.4.20241024
2. Last SHAFT_Engine version that did not exhibit the issue (if applicable): latest used directly
3. Desktop OS: Windows 10
4. Desktop Browser (if applicable): chrome
5. Desktop Browser Version (if applicable): 131.0.6778.205
6. Mobile Device Name (if applicable): -
7. Mobile Device OS (if applicable): -
8. Mobile Device Browser or Native App: -
9. Mobile Device Browser (if applicable): -
10. Mobile Device Browser Version (if applicable): -

To Reproduce
(Real project not a public access project)

Steps to reproduce the behavior:

1. Go to 'My requests' list
2. Search for the request.
3. Click on the 'request number' link
4. From the opened request details page pick the dammed status field text and validate its value
5. See error: stale element not found in the current frame

Expected behavior
Assertion passed by matching the status field gets text and the expected text

Screenshots

Additional context

Add any other relevant context about the problem here.

[MohabMohie]

provided sample is using assertions and related to the old element actions core.
this issue is not applicable for click/type and new element core actions class.

@kholoodGamal can you kindly provide a sample focusing on the click/type isse? I understand the assertions issue and will work on it.

[kholoodGamal]

@MohabMohie ThanQ, I will try to reproduce the Click/type case.

Could U please just clarify the meaning of "new element core actions class" as I didn't get the point and the guide reference refer to the same syntax.