RunMyJobs (EMEA)
Redwood SoftwareReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
312 reviews
from
External reviews are not included in the AWS star rating for the product.
Live Telemetry and SLA Dashboards That Keep Us Ahead of Failures
What do you like best about the product?
The real game-changer is the live telemetry. Having SLA-tracking dashboards that actually keep pace with our workload means we aren’t "hunting" for failures anymore. If a process lags even by a minute, the SMS alert hits our phones immediately, giving us a head start we never had before
What do you dislike about the product?
RunMyJobs has given us a "glass house" view of our entire automation stack. The automated SMS/Email triggers for schedule slips mean our oversight is now instantaneous. That level of transparency has fundamentally matured our operational response
What problems is the product solving and how is that benefiting you?
The end-to-end visibility via live SLA dashboards is unmatched. No more "wait and see"—the instant a job deviates, we get an alert. It has completely removed the guesswork from our monitoring
Eliminated Manual Check-Ins with an Exception-Based Model That Runs Itself
What do you like best about the product?
We’ve effectively eliminated about a third of our manual check-ins. Our mornings no longer start with a “health check” checklist; instead, we’ve shifted to a purely exception-based model that largely runs itself. and made our life easier.
What do you dislike about the product?
We’ve seen a 33.7% drop in "firefighting" mode. By automating the mundane validations, we’ve reclaimed our mornings, turning a manual grind into a high-speed, streamlined workflow and other features.
What problems is the product solving and how is that benefiting you?
We’ve cut our troubleshooting overhead by over a third. We went from manual daily monitoring to a system that only asks for our attention when it actually needs it. and make work much more faster.
Live Telemetry and SLA Dashboards That Keep Us In the Know
What do you like best about the product?
The real win for us is the live telemetry. Having SLA dashboards that actually mirror reality means we aren’t guessing; the second a process lags, the SMS alert hits our phones. It’s moved us from "guessing" to "knowing" in real-time.
What do you dislike about the product?
The transparency provided by the end-to-end monitoring suite is a total game-changer. We’ve set up a fail-safe environment where missed deadlines trigger immediate notifications, ensuring nothing ever stays "broken" in the dark
What problems is the product solving and how is that benefiting you?
Honestly, the SMS/email alert system is the backbone of our current setup. It’s given us total visibility into our job pipeline, so the moment an SLA is at risk, we’re already on top of it
Excellent Product—Would Love More Granular Error Diagnostics in the UI
What do you like best about the product?
If I could change one thing, it’d be the surface-level error messaging. Getting more granular diagnostic data directly in the UI would save us the headache of diving into raw logs every time something blips much
What do you dislike about the product?
There’s a slight bottleneck when errors occur because the UI messages are a bit vague. We’d love to see the "why" behind a failure up-front, rather than spending time piece-to-piecing it together from the logs and response
What problems is the product solving and how is that benefiting you?
The error reporting in the interface can be a bit of a "black box." Providing more "under-the-hood" detail within the alert itself would save our team a ton of manual troubleshooting
Retired the Morning Fire Drill with Automated, Exception-Based Operations
What do you like best about the product?
We’ve effectively retired the "morning fire drill." By automating manual checks, we’ve reclaimed 12% of our bandwidth and pivoted to a true exception-based operation
What do you dislike about the product?
We’ve slashed manual intervention by over 12.5%. Our team has successfully transitioned from reactive firefighting to a streamlined, automated oversight model
What problems is the product solving and how is that benefiting you?
We’ve cut "firefighting" by 12.45%. The morning routine is no longer a checklist—it’s a fully automated, exception-only process
Needs Deeper, At-a-Glance UI Diagnostics to Cut Raw Log Hunting
What do you like best about the product?
UI error reporting can feel like a riddle. We’re looking for deeper, "at-a-glance" diagnostics to replace the current hunt through raw logs at 90 %
What do you dislike about the product?
UI-level error granularity needs a boost. Surfacing specific diagnostic breadcrumbs upfront would save us from the manual labor of log diving 50 %
What problems is the product solving and how is that benefiting you?
Boost more UI error clarity. More specific diagnostic data on the surface would eliminate the need for manual log analysis
Enhancing RPA Control, Monitoring, and Scheduling Through Enterprise Orchestration
What do you like best about the product?
From an RPA perspective, what I really like about RunMyJobs is how it brings structure and control to bot operations. In many organizations, bots run independently or are scheduled directly within the RPA tool. With RunMyJobs, though, we can integrate bot execution into broader enterprise workflows.
For example, we use it to trigger bots only after specific ERP jobs have completed, or when a file is received from another system. This cuts down on manual coordination between teams and helps ensure everything runs in the right order.
I also value the centralized monitoring. Instead of logging into multiple systems just to check bot status, we can track everything from a single dashboard. The alerts and notifications are especially helpful for reducing downtime.
Overall, it makes our RPA operations feel more mature and enterprise-ready, rather than a set of standalone automations.
For example, we use it to trigger bots only after specific ERP jobs have completed, or when a file is received from another system. This cuts down on manual coordination between teams and helps ensure everything runs in the right order.
I also value the centralized monitoring. Instead of logging into multiple systems just to check bot status, we can track everything from a single dashboard. The alerts and notifications are especially helpful for reducing downtime.
Overall, it makes our RPA operations feel more mature and enterprise-ready, rather than a set of standalone automations.
What do you dislike about the product?
At first, it takes a bit of time to understand how to design complex workflows with multiple dependencies. For anyone new to workload automation, there’s definitely a learning curve.
In environments where many bots and systems are interconnected, troubleshooting can also require fairly detailed analysis to pinpoint what’s happening. A more simplified, clearer visualization of job chains would make it easier for support teams to follow dependencies and resolve issues faster.
In environments where many bots and systems are interconnected, troubleshooting can also require fairly detailed analysis to pinpoint what’s happening. A more simplified, clearer visualization of job chains would make it easier for support teams to follow dependencies and resolve issues faster.
What problems is the product solving and how is that benefiting you?
Before using RunMyJobs, scheduling and monitoring our bots took much more manual effort. When something failed, it wasn’t always obvious right away unless someone happened to check.
Now, bot execution is automated based on business events, and failures trigger alerts immediately. The restart mechanisms also cut down on manual intervention, and cross-system workflows run smoothly without constant follow-up.
Overall, it has improved reliability, reduced operational stress, and increased our confidence in our automation processes.
Now, bot execution is automated based on business events, and failures trigger alerts immediately. The restart mechanisms also cut down on manual intervention, and cross-system workflows run smoothly without constant follow-up.
Overall, it has improved reliability, reduced operational stress, and increased our confidence in our automation processes.
Streamlined Exception-Only Automation That Eliminated Morning Firefighting
What do you like best about the product?
We’ve effectively killed the morning "check-and-pray" routine. Firefighting is down by 41%, replaced by a streamlined, exception-only engine
What do you dislike about the product?
We’ve reclaimed 41% of our capacity. By moving to an automated, exception-based model, we’ve traded tedious manual oversight for pure operational flow
What problems is the product solving and how is that benefiting you?
We’ve officially retired the "manual morning checklist." With a 41% drop in firefighting, we now only step in when the system asks us to
Cross-Platform Control Tower for SAP, Cloud, and File Transfers
What do you like best about the product?
The cross-platform capability is the biggest win for me. We run workloads across SAP, file transfers, cloud services, and internal applications. RMJ gives us one control tower view. It also handles error handling intelligently, which reduces repetitive incident tickets.
What do you dislike about the product?
Initial implementation required careful planning. If you migrate too quickly without restructuring job logic, you’ll carry old inefficiencies into the new system. It demands discipline
What problems is the product solving and how is that benefiting you?
We struggled with fragmented automation tools. Each team had its own scripts and schedulers. RMJ unified everything. Now troubleshooting is faster because everything is visible in one dashboard. For me, that means less firefighting and more strategic improvement work.
RunMyJobs Simplifies Job Dependencies with Clear Visual Flows and Smart Alerts
What do you like best about the product?
What I like most is the way it handles job dependencies without making things overly complicated. In my previous company, we had multiple scripts scheduled separately and tracking failures was painful. With RunMyJobs, the visual chain flow makes it easy to identify which upstream job caused a failure. I also appreciate the alert customization — we reduced unnecessary email noise by configuring targeted alerts.
It solved our overnight batch monitoring issues. Earlier, we needed 2–3 people to manually monitor job completion. Now
It solved our overnight batch monitoring issues. Earlier, we needed 2–3 people to manually monitor job completion. Now
What do you dislike about the product?
The SAP integration is very stable. We run multiple SAP background jobs, and RunMyJobs centralizes everything instead of checking SM37 in different systems. I especially like the calendar configuration — it handles fiscal calendars well, which is important in finance environments
What problems is the product solving and how is that benefiting you?
like the parameterization flexibility. We run data loads daily with changing file names and timestamps. Dynamic variables help automate that without rewriting scripts.
The biggest advantage is centralization. We manage cloud jobs, database scripts, SAP processes, and file transfers in one platform. I also appreciate the audit trail — it helps during internal reviews and compliance checks. The object-based design makes reusable components possible
The biggest advantage is centralization. We manage cloud jobs, database scripts, SAP processes, and file transfers in one platform. I also appreciate the audit trail — it helps during internal reviews and compliance checks. The object-based design makes reusable components possible
showing 71 - 80