Bret B.

i have that info as well 🧠

My company had a runaway issue with Okta service accounts. Accounts made for a purpose and not a human. The ran to 10% of all licenses in Okta. I built an automation to be used as a Quarterly Access Review in Workato for all of these accounts. It uses Workato’s Web App to generate tasks for all of the known owners to review, certify or update the information associated with the account. It also gets security information about the accounts such as MFA enrollment and password age. First round of using it resulted in just shy of 10% of those accounts getting deleted. Plus the review only has around 50% completion due to bugs I missed during the design phase.

then the errors are all logged into here

Try the Log Message to Job Report and Workato Logs

seemed to have been a blip, its back now

I am facing the same

again i don't use this tool so i cannot verify but this is what Google/AI has to say

The error occurs because IBM MQ's classic JMS Client (WMQInitialContextFactory) requires the legacy javax.jms API, but your On-Premises Agent (OPA) environment currently only has Jakarta JMS 3.0+ (jakarta.jms), which moved from the javax namespace to jakarta. IBM MQ client libraries (specifically version 9.2 and older, or standard v9.3 com.ibm.mq.allclient.jar) expect the javax.jms classes. Here is how to resolve the missing class error. Step-by-Step Fix 1.Download the Legacy javax.jms Library:Required JAR.Download the JMS 2.0 API JAR file containing the javax.jms namespace.

Verification: Confirm the downloaded file is named javax.jms-api-2.0.1.jar (or javax.jms-api-2.0.jar). 2.Add javax.jms and IBM MQ Client to OPA Library Directory:OPA Configuration.Copy the javax.jms-api-2.0.1.jar file along with com.ibm.mq.allclient.jar into the OPA user extensions directory:

Note: Do not delete jakarta.jms-api-3.1.0.jar if other connectors rely on it, as Java can load both packages side-by-side because javax.jms and jakarta.jms use different package namespaces. Verification: Run ls -l (Linux) or check File Explorer (Windows) in the ext folder to verify both com.ibm.mq.allclient.jar and javax.jms-api-2.0.1.jar are present in the same folder. 3.Restart the Workato On-Premises Agent Service:Apply Changes.Restart the agent service so Java loads the new JAR into the classpath:

Verification: Open agent.log in the OPA logs/ directory and verify no classpath conflicts or missing class warnings occur during startup. 4.Retest the Connection in Workato:Workato Console.Navigate back to your Workato JMS connection configuration and click Test Connection. Verification: The connection test should pass without returning NoClassDefFoundError: javax/jms/ConnectionFactory.

sorry I do not use this tool so i am unsure how it works. i will look into some documentation and see if i can figure it out

have not Aaron W.