classic
I believe you also re-created the job scheduling board once or twice in your career, yeah?
We have our own Scheduling Dashboard. Most of the logic flow was built by @jgiese.wci If you build a solid Updatable BAQ in Classic, you are only limited by your imagination. Kinetic tooling still needs work.
Our Schedulers can tinker with the data and have a one-stop shop to run MRP etc…
We have a timeline, but I think everyone prefers the grid.
They can also create Maintenance Changeover Jobs automatically, and schedule individually. But most just use the sequence on the grid and then re-sequence all jobs and re-run Global Scheduling.
If they want more information they can always use Open With → Some Tracker
They can Engineer, Release Jobs etc on this Dashboard, they live and die inside of it. Atleast a guy named Jimmy does 
We don’t use Production Detail or Dispatch Paper Reports. Im surprised we even use Job Travelers still.
The Operators don’t use Epicor MES… For them we also build a Dashboard in Classic… but converted it to a Web App in Electron, for maximum customization. Josh added realtime websockets so data changes on the fly. Notifications. Messages. Auto-Update…
that’s how you know it works, that’s sick.
We are experiencing the same issue; making scheduling impossible. I have a case going with EpicCare - they did note my case is “connected to Major Case - CS0005599276” but I’ve not been able to find anything related to that case number on EpicCare.
It’s shocking this issue was known and recorded in the Problem Repository (PRB0320656) back on 7/21/26 and they pushed the update out regardless. The fix is completed per the PRB - they need to deploy a hotfix asap.
Will be reaching out to our CAM next.
I was told by the individual assigned to our ticket that 100.12 is set to release on 9/2… I sure hope that is correct and they have not gotten around to updating that table…
Released and available for cloud are two different things . . .
Here is the response from support via my ticket…
*A UDR and Hot Fix escalation have already been submitted, and the issue is currently being reviewed by Development.
Support has completed all available troubleshooting and escalation paths for this issue at this time.
As you stated, the current target fix is 2026.100.12.
However, there is also a Hot Fix request under review, so a fix could potentially be made available sooner if that request is approved.
Unfortunately, I do not have a timeline for the Hot Fix review process. As soon as there is an update, it will be posted to the Problem record.*
Off Topic EpiUsers Post Question:
When adding additional information a post such as this, is the protocol to reply to ones own post or to edit the original?
Hi All,
Update from support as of this morning is that a hotfix to address this has been approved and they will be working on that this week.
They are aiming to have it ready by the end of this week, or early next week.
I can’t really share the application itself because it was built specifically around our environment and is pretty tightly integrated. But I put together a write up of the approach, services, workflow, and schemas that should help you build something similar.
SHAREABLE_EPICOR_SCHEDULING_BOARD_GUIDE.md (21.1 KB)
One thing that sped up the process a lot was downloading HAR files from the browser Network tab while using Epicor’s Resource Scheduling Board, then using AI to analyze them and reverse engineer the service calls and request flow.
I think Hotfix K is out for 2026.100.9 that will fix this issue, but it is hard to tell because support isn’t just flat out saying that. Instead i was told about the Hotfix on another less important Scheduling board issue that they linked to the same problem at some point. I am trying to apply this new K hotfix in Pilot, but I don’t think it is available there. Does anyone have more insight?
We were also told it was available, but it’s not showing in CMP.
Same, got an update saying it was available, but nothing is showing up in the list on CMP.
seems stupid but you will still have to put a ticket in with support for them to apply the hot fix to your tenant instance
We have been updated to the hotfix in both pilot and live and Job Scheduling Board is back and operation.
Same for us. Hotfix applied last night fixed the issue.
Chiming in here to say we also received the update in Pilot and can confirm it resolves it for us. Now to schedule for live.
anybody find any new issues to come out of this Hotfix?
Our purchasing department is reporting PO suggestions no longer show Supplier Pricelist Lead time accurately… so that’s one thing.
PRB0289286
PO suggestions - Order By does not honor to the lead time defined in the Supplier Price List (when Supplier Parts lead time = 0)