Level 6

Solved

Continued latency with receiving execution data from Fusion executions

Forum|Forum|23 days ago
April 29, 2026
5 replies
93 views

I posted something about this a while ago. However, the problem just keeps getting worse. I’ll trigger a scenario I’m working on by performing an action. The automation will run. And regardless of it runs successfully, it errors out, or returns a warning, I’m waiting for minutes before I can see what’s actually happening. I’m not the only person on my instance who is experiencing this. My colleague in a different business unit has to deal with the same latencies.

Yeah, I know that if you trigger individual modules when building, you get an almost instantaneous turnaround with execution data. Yeah, I know I manually start an automation, I’ll get execution data almost instantaneously. However, I’m in the midst of building a complicated automation which requires it get triggered from inside of Workfront. Every time I run it, I have to wait between three to five minutes before I get any data back. And even when I get a failure pop up on my screen, I’ll go to the scenario where I’m still waiting for at least a minute before I get usable, actionable data.

At least a year ago, this wasn’t an issue. But it’s gotten more and more annoying the more and more I’m doing complicated work and I’m basically sitting around before I can see what happened and/or going to get more coffee.

Are others still dealing with this? And, if so, is there anything being done to return usable, actionable data in a more snappy way?

BTW: I’m writing this now waiting for the data to come back from my most recent execution. At least I’m using my time effectively lol.

Best answer by JohnJOSullivan

Just as an update, I put a support ticket in concerning this issue. I have wasted hours of my life the past month. The notes were sent to product and engineering, but there is no promise that this will be addressed.

Heather_Kulbacki

Community Advisor

We’re experiencing this, just this week especially with scenarios that edit expenses. When an expense report has been reimbursed in our financial system we pass the expense report number and ID back to the corresponding expense objects in WF - no more than 10 objects at a time from a given expense report.

Our scenario is timing out before it can get just 2 fields written on 10 expense objects.

Even manually editing an expense object, it’s taking forever to save.

JohnJOSullivanAuthor

Level 6

I’ve noticed even greater latencies when using HTTP calls from scenario to scenario. Example: I have a main scenario which grabs relevant documents to send to our AEM instance. The second scenario is the one which does the work uploading documents and transferring metadata. Just before, it took about three minutes for the child scenario to get called. When you’re testing things and you want to just be sure it’s working….watching a Fusion screen sit there and do nothing for minutes is extremely frustrating.

(Yeah, I know about the new chains functionality, which I’m really looking forward to using. That said, I tried using it...and the thing told me that it couldn’t call itself to activate the child scenario. It’s beta so weirdness is expected, so I want that more fully baked before I use it for prime time.)

KristenS_WF

Level 7

I’ve got 2 scenarios that are scheduled to run at 2 pm each week day. I almost filed a support ticket just now because there was nothing showing that my scenarios had run--no history or even (the slow) processing history statuses. I closed Fusion altogether and reopened it just in case. It was over 10 full minutes before anything showed up under history.

KristenS_WF

Level 7

So, those two schedules scenarios? They ran, but the history still shows them as processing. Something was definitely messed up yesterday.

JohnJOSullivanAuthor

Level 6

I def think something was up. I had continual minutes-longs latencies with two scenarios with custom webhooks. I checked the overall instance performance when they were running and the system was *not* taxed with being under-resourced.

ninoskuflic

Level 5

I’m experiencing this issue almost every day, and it’s becoming quite frustrating. It would be great if Adobe could take a closer look at it.

It seems like the problem started after Fusion was migrated to the new architecture as before that I never encountered this issue.

If this solved your issue, please mark it as solved so others can find the solution faster.

JohnJOSullivanAuthor

Level 6

That seems to be the case. I never had this problem previously. But this has likely cost me hours of productive time just to get the data I need to tweak or modify my scenario during a build.

ninoskuflic

Level 5

I just opt in to manually running the scenario before triggering stuff in Workfront. I can’t deal with these waiting games 😂

If this solved your issue, please mark it as solved so others can find the solution faster.

KatherineLa

Community Advisor

My instance are seeing weird time-out/latency errors, and connection failures as well. I hadn’t connected them to any particular upgrade until just now, so we hadn’t opened tickets for help. I’ll start doing that as they pop up now though.

JohnJOSullivanAuthor

Level 6

I just had an automation which relies on a custom webhook take a minute to receive data. This has been more common lately. And of course I’m working on two major projects.

And then, when the webhook finishes the process, it takes 2-3 minutes to get execution data. I have wasted hours of my life just waiting for data.

JohnJOSullivanAuthorAccepted solution

Level 6

Just as an update, I put a support ticket in concerning this issue. I have wasted hours of my life the past month. The notes were sent to product and engineering, but there is no promise that this will be addressed.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded