Share via

element not found

Mohamed Adel 0 Reputation points
2026-04-29T13:52:15.64+00:00

Correlation Id: d3ff7810-03c1-4505-ac7d-bf103304ef11

Microsoft.Flow.RPA.Desktop.Modules.SDK.Extended.Exceptions.InternalActionException: Element with selector '> body > div > div > div > div > iframe[Src="/webui/servlet/standalone/../fslogin?applicationId=51226&standalone=true&"] label[Id="node-tfacr2411m000-label"]' not found.

at Microsoft.Flow.RPA.Desktop.Modules.WebAutomation.Actions.ClickBase.Execute(ActionContext context)

at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary2 inputArguments, Dictionary2 outputArguments)

Microsoft 365 and Office | Install, redeem, activate | Other | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-04-29T13:52:28.61+00:00

    The error indicates that the web automation action in the desktop flow cannot find the web element that matches the stored CSS selector:

    > body > div > div > div > div > iframe[Src="/webui/servlet/standalone/../fslogin?applicationId=51226&standalone=true&"] label[Id="node-tfacr2411m000-label"]

    This typically happens when the page structure or attributes have changed since the element was first captured.

    To resolve the issue:

    1. Reopen the target web page and navigate to the exact state where the element should be available.
    2. In Power Automate for desktop, open the desktop flow and locate the failing web action (for example, Click link / Click element / Press button) that uses this selector.
    3. Use the selector editor to repair the selector:
      • Select the UI element used by the action.
      • Choose the Repair option and recapture the element on the live page.
      • Review the proposed selector changes and save them.
      • Then use Test in the selector editor to confirm that the element is found successfully.

    If the page is highly dynamic (for example, IDs or structure change frequently), adjust the selector to be more robust:

    • Prefer stable attributes (such as consistent classes, text, or higher‑level containers) over volatile IDs.
    • Avoid over‑specific full DOM paths when possible.

    If the failure occurs only in unattended runs, also verify that the unattended environment renders the page the same way as during design (same screen resolution, same browser, same zoom level), because layout changes can affect which elements are present or visible.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.