If I get something I don’t like, I escalate the case or create a new case when a new instance of the issue occurs and link the previous case. Maybe I’m the problem, but I get responses when I do that.
I do that too, nothing but silence.
2 Likes
My case has been escalated for about 5 months. (it is also the second case opened on that issue, the first was closed)
1 Like
From “Kinetic in the Cloud 2025.1 Calendar” -
Saturday, August 23 - Sunday, August 24, 2025 - 2025.1.11 Production Update for All Datacenters - Quality enhancements to your Production environment.
I don’t think we could have caught this bug any sooner than Aug 25 
and there is no mention of scheduled tasks or a workaround for SSRS in Scheduled Tasks.
5 Likes
Support operates within the same reality our customers do. We don’t work in “what could be” or “what should be”–our purview is what is. The workarounds documented in our knowledge articles and problem records reflect the options Support can offer to help customers keep moving.
This isn’t an attempt to influence how anyone should feel about those options, or the situation that led to these options being suggested. Our goal has always been, and will continue to be, to identify any viable path that helps customers achieve their desired outcome if at all humanly possible. Even if the option isn’t ideal, offering something is better than offering nothing.
For full transparency: I am the author of the SUPPORT BULLETIN article and the four linked knowledge articles referenced within it(or one of the other linked articles) including the WHITEPAPER that I felt a moral imperative to spend my weekend creating–which I first shared in this thread.
3 Likes
Waiting 5 minutes to see if a report fails while constantly monitoring a laggy System Monitor isn’t keeping us moving. It’s a huge waste of time and a massive morale killer. “Execute it again” isn’t helpful. It’s not a workaround.
4 Likes
@aidacra, while you personally worked on the bulletin and the articles supporting it, I am hoping that we can kindly convey the frustration we are receiving from our users, my CFO, and several others without insulting you or souring our relationship. When things get terribly bad with someone, I will explain to them that, “I am not Epicor or your problems, so please don’t treat me like them”… after which I continue trying to work on the issue and stay kind. I assure you I am trying my best to be as kind as I can be given the amount of pressure we are each under. I am sure you can imagine the look on my CFOs face when I tell him that the workaround is to “try again” after he’s spent the last 45 minutes trying to print a summarized general ledger report for the month of October in 2025 for a company with 15 user licenses. The CFO, CEO… they’ll never be okay with that workaround for the money they are spending on this software and offering that workaround to them only lessens my credibility with them because it’s absolutely not acceptable. I still told them the workaround, and I’ll continue to say it because that’s all there is like you said, but we are in a bad spot.
I’m kindly and respectfully saying this SSRS issue is extremely frustrating and at the same time saying @aidacra, you have always been there for us, and I thank you for that. You have helped me throughout my career, I’ve listened to you speak at EUG meetings in Kalamazoo, Michigan and still share that content today with people who are having printing issues and the like. Your knowledge and procedures on debugging have been helpful to study and use as well- they gave me the confidence needed to troubleshoot app server memory issues, etc.
Thanks for everything you do. It’s hard only hearing about issues every day and when it starts working as normal, when we finally fix it, nobody really cares because from the end user’s perspective it never should have been broken in the first place… so we move onto the next issue and the cycle repeats. I have kindness in my heart, kindness for you @aidacra. If there’s anything we can do as a user group to help your team or test something you know we all will, we’ve been trying to figure this out for months so please let us know if there’s anything we can do. I know you and your team are doing the best you can, and I appreciate that you’ve taken this issue up personally. We are in good hands. It took courage to post a work around such as that, knowing that it’s not ideal and it’s the only thing that could be offered, and it took time and effort on a weekend, nonetheless. That’s dedication. Thank you.
Looking forward to continued progress on this. Thanks again for popping in here. You write well; do you read a lot? It would have taken me hours to compose the items you’ve posted in this thread let alone the bulletins and KB articles you had to draft as well 
. Thanks for everything Nathan.
15 Likes