Fusion scenario troubleshooting | Community
Skip to main content
JustinWa2
Level 4
May 14, 2026
Question

Fusion scenario troubleshooting

  • May 14, 2026
  • 3 replies
  • 86 views

Hello! I have a scenario that has stopped working as intended on proofs. It shows no errors within the scenario so I know it’s active and running, but it doesn’t do what it used to and I’m a novice at Fusion so I can’t seem to figure out what’s happened. Anyone know a good resource to use to troubleshoot? 

    3 replies

    tekmera
    Level 2
    May 14, 2026

    Hi ​@JustinWa2 could you post some screenshots? 

     

    In the meantime, here’s a link to the Workfront Experience League Documentation for the proof connector. - https://experienceleague.adobe.com/en/docs/workfront-fusion/using/references/apps-and-their-modules/adobe-connectors/workfront-proof-modules

    David Kershaw | Workfront & Fusion Architecture | Tekmera | https://tekmera.ai/work-with-us/adobe-practice
    ninoskuflic
    Level 5
    May 15, 2026

    As ​@tekmera said, few screenshots, explanation of what the scenario was doing / is supposed to be doing would help us to help you. 😊 Also, when did it stop working, did something change in the environment? 

    If this solved your issue, please mark it as solved so others can find the solution faster.
    JustinWa2
    JustinWa2Author
    Level 4
    May 21, 2026

     

    Okay, here are screenshots starting with the scenario as a whole and then, in succession of the intended path of the scenario, what each module and filter does. I’m not sure when it first stopped working, but I believe it was 6-8 weeks ago.  

    Here’s the whole reasoning behind it: Our international teams use an automated workflow when uploading proofs that determines who should be on the proof and in what role and stage they should be on. This is done through a separate scenario.  We found that when uploading a V2, V3, V4, etc… of the proof, the users who marked approved, approved with changes, or not relevant on a previous version were remaining as approvers and being required to once again provide a decision. We had this scenario created to fix that issue. It’s intent was to identify any user who had  rendered a decision other than changes required on the previous version of a proof and switch their role to reviewer on all subsequent versions of the proof. 

    The scenario is active and running it’s just not doing what it’s supposed to do.

    Thanks for any insights!

    ninoskuflic
    Level 5
    May 21, 2026

    Did you check the execution log? On what stage (module) does it fail or not do what it’s supposed to be doing? Or does it not trigger at all? 

    If this solved your issue, please mark it as solved so others can find the solution faster.
    JustinWa2
    JustinWa2Author
    Level 4
    June 4, 2026

    Sure thing, first shot is of iterator 25, second is the filter after iterator 25, third is iterator 35, and fourth is the filter after iterator 35