Legacy accounts experience slow Forge macro remounts after configuration changes

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • Component/s: Ecosystem
    • None
    • 1
    • Minor
    • 3

      Issue Summary

      Following a site transfer , legacy Atlassian accounts are experiencing an issue where Forge macros—specifically the SharePoint app—did not automatically reload after configuration changes.

      A feature-gate adjustment by the Forge UI team restored the remount functionality. However, the remount/reload process is now consistently slow for legacy accounts, taking several seconds. Newly created accounts do not show the same delay and reload almost instantly.

      The issue appears to affect accounts with legacy identity or consent states that existed before the site transfer.

      Steps to Reproduce

      1. Step 1: log in conflunece site using legacy account. 
      2. Step 2: Open a page containing the SharePoint Forge macro
      3. Step 3: Open the macro editor-> Modify a macro property or configuration.
      4. Step 4: Save the change.
      5. Step 5: Observe the time taken for the macro iframe to remount/reload.
      6. Step 6: Repeat the same steps using a newly created account.

      Expected Results

      The Forge macro iframe should remount and reload promptly after a configuration change, with behavior comparable to a newly created account.

      Actual Results

      For legacy accounts, the Forge macro iframe remounts/reloads only after a delay of several seconds. The UI appears stalled during the remount process. 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Unassigned
              Reporter:
              Divyshri Jain
              Votes:
              11 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: