Hello Carlos Bahamonde Vera ,

This error usually happens after updating OutSystems UI dependencies when some screens/layouts are still referencing older accessibility logic (especially around menu components like LayoutTopMenu). The framework tries to check the role attribute on an element that is no longer present in the DOM after the update, which breaks the script during screen load. It’s typically a dependency version mismatch or incomplete republish issue, not a functional coding mistake.

Try the following steps:

• Open Manage Dependencies and refresh all OutSystems UI references.
• Ensure your module is using the latest compatible OutSystems UI version.
• Republish the Layout module first, then the consumer modules.
• Run 1-Click Publish on the solution (recommended after framework updates).
• Clear browser cache / test in incognito mode.
• If still failing, re-drop the LayoutTopMenu pattern once and republish.

Best practice: after upgrading platform or UI dependencies, always republish the base layout + theme + dependent modules together, because accessibility updates (like role attribute handling) often affect shared layout scripts.

This usually resolves the “element does not exist while checking attribute role” error without additional changes. ✅

Thanks and Regards,
Akshay Deshpande