What is our primary use case?
My main use case for JAMS Scheduler is scheduling daily RPA jobs, such as running an invoice process automation after the source files are available. JAMS Scheduler manages the job sequence and dependencies, and I use it to monitor the execution and handle failures.
One thing I find useful is managing dependencies between multiple automation jobs. For example, I can configure the RPA process to start only after the previous job completes successfully, which helps keep the workflow organized and reliable.
What is most valuable?
The best features JAMS Scheduler offers, which I found most useful, include job scheduling, dependency management, monitoring, and failure handling. In my day-to-day work, these features make it easier to automate recurring RPA workflows and quickly identify issues when a job doesn't complete as expected.
Regarding monitoring and failure handling, I find the alerting and notification system reliable. The alerting is useful for day-to-day monitoring, especially for failed or delayed jobs, and I can configure notifications for critical jobs so the support team can investigate quickly instead of manually checking every job.
The centralized view of scheduling jobs and their execution status gives me a clear picture of the automation workflow, which is helpful when multiple RPA processes are running on different schedules.
Although I don't have formal metrics, using JAMS Scheduler has reduced the amount of manual monitoring needed for our scheduled RPA jobs. It also helps reduce missed or delayed executions because jobs, job dependencies, and failures are handled through a centralized scheduler.
What needs improvement?
One area of improvement I see for JAMS Scheduler is making the user interface more intuitive for new users, especially when configuring complex job dependencies. Better documentation on advanced scheduling scenarios would also help reduce the learning curve.
For onboarding a new user, practical examples and step-by-step templates for common RPA scheduling scenarios would be helpful. For daily use, a simpler way to troubleshoot failed jobs and understand dependency issues would make the experience smoother for newer users.
For how long have I used the solution?
I have been using JAMS Scheduler for around one year.
What do I think about the stability of the solution?
JAMS Scheduler has been stable for our day-to-day RPA scheduling. The scheduled jobs generally run consistently, and when issues occur, the monitoring and execution logs make it easier to identify and recover from them.
What do I think about the scalability of the solution?
JAMS Scheduler has scaled very well for our RPA environment. As the number of scheduled jobs increased, we can manage multiple schedules, dependencies, and workflows centrally, which makes it easier to add new automations without significantly changing the existing setup.
How are customer service and support?
The customer support experience has been generally good for the issues we have raised. For example, we had questions around job configuration or troubleshooting, and the available documentation support helped us resolve them without major disruption.
I would rate customer support eight out of ten. The support has been helpful for configuration and troubleshooting questions, although response times can vary depending on the complexity of the issue.
Which solution did I use previously and why did I switch?
Before JAMS Scheduler, we mainly used basic OS-level scheduling and manual triggers for some automation jobs. We switched to JAMS Scheduler as the number of jobs increased, and we needed better dependency management, centralized monitoring, and failure handling.
How was the initial setup?
I wasn't directly involved in the procurement or licensing negotiations for JAMS Scheduler, so I don't have enough visibility into the exact pricing or the setup cost. For the implementation side, the main effort was around configuration, jobs, dependencies, and integrations with our existing RPA environment.
What was our ROI?
We have seen a practical return on investment, mainly through reduced manual monitoring and fewer missed job executions. For example, a daily invoice automation that previously required manual scheduling and monitoring can now run automatically through JAMS Scheduler, saving the team recurring effort and allowing them to focus on exception handling.
Which other solutions did I evaluate?
We briefly considered using native Windows Task Scheduler and some other enterprise scheduling tools before choosing JAMS Scheduler. Ultimately, we focused on JAMS Scheduler because it provided centralized scheduling, dependency management, monitoring, and interaction capabilities that fit our RPA environment.
What other advice do I have?
JAMS Scheduler's code-driven automation has helped handle complex scheduling requirements, which is important for our organization. This is because it gives us more flexibility than managing every scenario manually through the interface.
JAMS Scheduler has helped notify and handle common issues that prevent my jobs from running. Common issues include incorrect schedules, unavailable source files, failed dependencies, and connectivity problems.
I do use JAMS Scheduler's interactive agents, and adding interactive processes is important when an automation requires user input or interaction with a desktop application. In our RPA environment, they can help support processes that cannot run completely unattended while still allowing JAMS Scheduler to manage the scheduling and execution.
Running interactive tasks does help users focus on their business processes. This is important for our organization because it reduces the need to manually monitor routine automation tasks. JAMS Scheduler can schedule the interactive tasks at the required time while users step in only when their input or intervention is needed.
JAMS Scheduler has helped centralize the management of jobs across all our platforms and applications. This is important because it gives the team one place to manage schedules, dependencies, and job statuses instead of handling each automation separately.
I would rate JAMS Scheduler an overall eight out of ten.
Which deployment model are you using for this solution?
On-premises