BPM Automation Studio Widget down - Only fixing for 2025.1.16

Kinetic ERP
21

Why can’t the fix be included for all supported Kinetic versions? It’s extremely unfair to only fix it in 25.1.16. You know as well as us that it’s not possible to just jump from 24.x to 25.1 overnight.

1 Like
22

Submit a ticket to support, there will probably be a Hotfix available

6 Likes
23

I’d like to clear up some of the information being shared in this thread.

  1. BACKGROUND:
  • This issue originated from a security-related change implemented by Workato. That change requires us to update the BPM Widget used to trigger Automation Studio workflows.
  1. Who Is Affected?
  • If you do not use the BPM Widget to trigger Automation Studio, you are not impacted.
  • If you do use the BPM Widget, your existing automations will continue to work as long as you don’t modify them.
  • The issue only occurs if you edit an existing BPM trigger or create a new BPM trigger that connects to Automation Studio.
  1. Fix and Support Policy:
  • The earlier message indicating that this would only be fixed in version 2025.1 was a miscommunication.
  • We plan to support fixes for this issue according to our standard lifecycle support policy.
  1. What to Do:
  • If you’re affected, please submit a support ticket to request a hotfix for your version, making sure that you inform support which version you are on.
24

Thanks Tim. Epicor has to fix their communication with customers. These emails that are incorrect aren’t helping anything.

4 Likes
25

@timshuwy for everyone not on EpiUsers that got that email is Epicor going to send a correction out?

1 Like
26

This thread was my only notification despite having Automation Studio running in our environment and using the BPM widget to call recipes so they probably also need to doublecheck how they’re pulling a list of customers to notify.

3 Likes
27

I believe so. Marketing is working on it.

2 Likes
28

Agreed. These unforced errors piling up and causing stress to us customers.

30

Thank you Tim for the follow up on this! Hopefully those that aren’t on here get the clarification email soon.

2 Likes
31

Epicor has provided additional details about required changes to BPMs using the Automation Studio widget. In case you didn’t get the email, the details are below.

12/8/2025 - Action Required: BPM Automation Studio Widget Fix Next Steps

Action Required: BPM Automation Studio Widget Fix Next Steps

We are pleased to inform you that a fix for the Automation Studio widget in BPM for Kinetic will be deployed as follows. Please read to learn about the widget fix schedule and your actions, including deleting legacy client API and re-registering your instance, to minimize disruption to your business. If you are not using the Automation Studio widget in BPM, then this does not apply to you.

  • Automation Studio : Saturday, December 13, 7:00 AM - 9:00 AM US Central Time
  • Kinetic Cloud: Saturday, December 13, 10:00 PM to Sunday, December 14, 4:00 AM Local Datacenter Time
  • Kinetic On-premises: As soon as possible following the Automation Studio deployment on December 13

What You Need to Do
To ensure your integration continues to work as expected, please delete the legacy API client in Automation Studio and re-register your Kinetic instance beginning Sunday, December 14, regardless of your Kinetic version.

This critical step is required due to Workato security and performance enhancements which impact the existing Automation Studio BPM widget.

Kinetic On-prem/Cloud Version Action
On-premises 2024.1 and above 1. Download the hotfix from EpicWeb, which will be available on December 12, 2025 2. Apply hot fix to all your applicable instances after Automation Studio changes 3. Follow the Automation Studio instructions available here
Kinetic Public Cloud, GovCloud, Life Sciences Enterprise Cloud, Multi-tenant NA Follow the Automation Studio instructions available here

FAQ

When will the fixed be deployed?

  • Cloud : Saturday, December 13, 10:00 PM to Sunday, December 14, 4:00 AM Local Datacenter Time
  • On-premises : As soon as possible following the Automation Studio deployment on December 13

What happens to existing integrations using Automation Studio BPM widgets?

  • Cloud : Your integration will stop working starting December 14. Deleting legacy API client in Automation Studio and re-registering the Kinetic instance is required to restore the functionality.
  • On-premises : Creating new integration using BPM Automation Studio widget or updating existing integration with BPM Automation Studio widget will work only if the hot fix is applied, the legacy API client deleted and re-registering the Kinetic instance

How can I minimize disruption?

  • Cloud: Delete the legacy API client and re-register (steps here) your instance as early as possible starting Sunday, December 14.
  • On-premises: Apply the hotfix, then immediately delete the legacy API client in AutomationStudio and then re-register (steps here) your Kinetic instance

How to delete the legacy API client in Automation Studio?
Follow the step-by-step instructions outlined in EpicWeb here.

How to re-register the Kinetic Instance in Automation Studio?
Follow the step-by-step instructions outlined in EpicWeb here.

We do not use Automation Studio widget in BPM, am I impacted?

No, if you are not using the Automation Studio widget in your Kinetic instance, then you are not impacted.

For additional questions, please submit via EpicCare.

4 Likes