​@SakthiVel A very  l-o-n-g  time ago, I saw something similar. When that happened, I was having a conflict between the plug-in installed in Chrome and the plug-in installed in Edge. Disabling the Chrome plug-in fixed the issue. Likewise, if you want to use Chrome, try disabling the Edge plug-in.

Let me know if that works for you.

i have only Edge browser , no Chrome installed 

Hi ​@SakthiVel,

In normal cases, the Plug-in disppearence can be caused by any of the below.

1. Edge policy flapping (Intune/Edge Management/GPO)

   • When the ExtensionInstallForcelist or ExtensionSettings policies temporarily drop (service hiccup, profile re‑eval, conflicting GPOs), Edge uninstalls managed extensions, then re‑applies them when policy returns—exactly the “gone, then back” loop you’re seeing. Multiple admins have reported Edge policies disappearing and later reappearing on managed devices; when policies are gone, edge://policy is empty and managed extensions vanish. 

2. MV2 vs MV3 “dual” Automation Anywhere extensions

   • Automation Anywhere now publishes Manifest V3 (MV3) extensions and has a deprecation path for MV2. Running with both variants (or being migrated by a management setting) can yield intermittent enable/disable states. The MV3 Edge add‑on is Automation 360 (ID visible on the store page), while the old MV2 page explicitly recommends switching to MV3. 

3. Multiple profiles / temporary profiles

   • Edge installs extensions per profile. If your bot launches Edge with a different profile, a guest profile, or a temporary --user-data-dir, extensions may be absent and (worse) Edge can remove extension folders when it re‑syncs profiles. Users have reproduced “extensions removed after restart or when using a different profile location.” 

4. Chrome vs Edge AA plug‑in conflict (less common but real)

   • AA’s own community has reported cases where having the AA plug‑in in both Chrome and Edge caused intermittent Edge behavior; disabling the Chrome plug‑in resolved it. Worth a quick A/B test on a runner where Edge is primary. 

5. Control Room “Browser extensions” settings manipulating policy

   • AA Control Room can push/toggle extension state on devices, but it relies on the OS policy ExtensionInstallForcelist. Certain toggles can delete the Forcelist policy on devices until re‑enabled—exactly the kind of loop that removes an extension and later puts it back. 

6. Edge updates

   • Some customers observe that after certain Stable updates, extensions disappear until a subsequent policy refresh. There are community reports of extensions being removed post‑update and after profile changes. Keeping to the latest 138 extended stable (or newer 139) can help, but the root is usually policy/profile behavior. 

Things you can try to find the root cause:

• When the bot fails, immediately open edge://policy and export; compare to a success run. Do you still see ExtensionInstallForcelist? (If no, it’s policy flapping.) 
• Check HKLM\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist right then. Did the value disappear? (If yes, the extension removal was policy‑driven.) 
• Confirm you have only one AA extension (MV3) under Edge → Extensions and remove/block MV2.