Why are all my connections broken? | Community
Skip to main content
amybillmayer
Level 4
March 11, 2026
Solved

Why are all my connections broken?

  • March 11, 2026
  • 2 replies
  • 52 views

I recently refreshed my SB01 and then discovered that all my Fusion scenarios connected to SB01 or Preview are broken. Has anyone else encountered this, and how do you restore the connections without having to rebuild the webhooks and api calls? 😭

    Best answer by amybillmayer

    Not the answer I was hoping for, but here’s what Workfront had to say:

    When you refresh your Adobe Workfront Sandbox, all data in the sandbox is replaced with a fresh copy of your production data. This process has a direct impact on Workfront Fusion connections:

    Why Fusion Connections Break After a Sandbox Refresh:

    • When the sandbox is refreshed, any Fusion connections that were previously authorized in the sandbox are invalidated. This is because the underlying authentication tokens, user IDs, and sometimes even the environment URLs can change or be reset as part of the refresh process.
    • You must re-create or re-authorize your Fusion connections in the sandbox after every refresh. This is expected behavior, not a one-time issue.

    Will They Break Again Next Time?

    • Yes, Fusion connections in your sandbox will break every time you refresh the sandbox. This is because the refresh process wipes the sandbox and re-clones it from production, invalidating previous connection authorizations and tokens.
    • This is a known limitation and a common scenario for all integrations and automations tied to the sandbox environment.

    What You Can Do:

    • After each sandbox refresh, plan to re-create or re-authorize your Fusion connections.
    • Consider documenting your connection setup process so you can quickly restore integrations after future refreshes.
    • This behavior is documented in both official Adobe Experience League documentation and internal best practices.

    2 replies

    Heather_Kulbacki
    Community Advisor
    Community Advisor
    March 11, 2026

    Were your Fusion connections for SB01 connected to a user that is no longer active?

    Maybe there were deactivated in Prod before now, but the refresh set them to deactivated in the sandbox now.

    amybillmayer
    Level 4
    March 11, 2026

    This would make perfect sense, but no. All the connections are using a generic account: fusion.dataconnect@a********.com - this “fake” user account is active in all our environments.

     

    The connections in Prod use the same account, but those didn’t break.

    amybillmayer
    amybillmayerAuthorAccepted solution
    Level 4
    March 11, 2026

    Not the answer I was hoping for, but here’s what Workfront had to say:

    When you refresh your Adobe Workfront Sandbox, all data in the sandbox is replaced with a fresh copy of your production data. This process has a direct impact on Workfront Fusion connections:

    Why Fusion Connections Break After a Sandbox Refresh:

    • When the sandbox is refreshed, any Fusion connections that were previously authorized in the sandbox are invalidated. This is because the underlying authentication tokens, user IDs, and sometimes even the environment URLs can change or be reset as part of the refresh process.
    • You must re-create or re-authorize your Fusion connections in the sandbox after every refresh. This is expected behavior, not a one-time issue.

    Will They Break Again Next Time?

    • Yes, Fusion connections in your sandbox will break every time you refresh the sandbox. This is because the refresh process wipes the sandbox and re-clones it from production, invalidating previous connection authorizations and tokens.
    • This is a known limitation and a common scenario for all integrations and automations tied to the sandbox environment.

    What You Can Do:

    • After each sandbox refresh, plan to re-create or re-authorize your Fusion connections.
    • Consider documenting your connection setup process so you can quickly restore integrations after future refreshes.
    • This behavior is documented in both official Adobe Experience League documentation and internal best practices.
    Heather_Kulbacki
    Community Advisor
    Community Advisor
    March 11, 2026

    @amybillmayer Did they mention if this is something new? We’ve refreshed our sandboxes numerous times. The most recent being Jan.31 and we’ve never had to re-authorize our connections.

    amybillmayer
    Level 4
    March 13, 2026

    Hi ​@Heather_Kulbacki - I asked, and this was the response I received:

    No this behavior related to the refresh is not new. Sandbox refreshes to align with Production. If there is a difference in authentication between the two such as password for connecting users, session or API key information, these can all be changed through a refresh, breaking the connection. Typically connections are setup with OAuth where a session is created to authorize your scenario modules as this user, per my last note, this will break each time as Sandbox is effectively re-created in a refresh removing any existing sessions.