Continued latency with receiving execution data from Fusion executions
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.