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.
Clean Core SaaS Scheduling That Seamlessly Integrates with SAP and Beyond
What do you like best about the product?
The "Clean Core" approach is the standout feature for us. Unlike legacy schedulers, RMJ is a SaaS solution that integrates directly with SAP S/4HANA, BTP, and ECC without requiring heavy on-premise infrastructure maintenance. The ability to import and export jobs between environments (transporting from Dev to Prod) is seamless and much easier than our previous tools. I also appreciate that it connects to both SAP and non-SAP systems in a single chain; for example, a job in SAP can trigger an OS-level script immediately after finishing.
What do you dislike about the product?
The out-of-the-box dashboarding is functional but feels limited; we often wish for more customizable visualization modules without having to build them from scratch. We also encountered specific issues with "variable variants" when trying to automate SARA archiving flows—the support for the full archiving flow (SUB to DEL) wasn't as smooth as expected
What problems is the product solving and how is that benefiting you?
It has solved the "End of Day" and "Month End" closing chaos. Previously, we needed multiple SAP Basis administrators just to manually monitor and submit repeatable jobs every 10 minutes. Now, we have consolidated ~46,000 job definitions down to about 570 reusable scripts. This reduced our administrative overhead significantly, allowing us to run operations with just one admin instead of six.
RunMyJobs: One Control Point Across Hybrid and Cloud Environments
What do you like best about the product?
I like that RMJ works well across hybrid and cloud environments. We run workloads on different platforms, and RMJ gives us a single control point without forcing us to redesign existing scripts.
What do you dislike about the product?
Some advanced features require deeper product knowledge, and documentation doesn’t always go far enough for complex scenarios. We sometimes rely on trial and error to fine-tune configurations.
What problems is the product solving and how is that benefiting you?
Solving and how it benefits me
RunMyJobs addresses the chaos of managing automation at scale. Instead of custom cron jobs and scattered tools, everything is centralized. That reduces deployment risk, improves visibility, and makes our automation strategy easier to maintain as the environment grows.
RunMyJobs addresses the chaos of managing automation at scale. Instead of custom cron jobs and scattered tools, everything is centralized. That reduces deployment risk, improves visibility, and makes our automation strategy easier to maintain as the environment grows.
Rock-Solid Stability and Clear Monitoring for High-Volume SAP Batch Jobs
What do you like best about the product?
What I like most is how stable it is once everything is configured properly. We run hundreds of SAP batch jobs daily, and RMJ rarely fails on its own.The monitoring dashboard gives me clarity without needing to check multiple tools.
What do you dislike about the product?
The UI feels slightly technical for new users. It’s powerful, but not very beginner-friendly. Also, troubleshooting sometimes requires deep understanding of job chains and parameters — not something junior team members can pick up quickly.
What problems is the product solving and how is that benefiting you?
Before RMJ, we had manual SAP background job monitoring, which was risky and time-consuming. Now everything is automated — financial postings, IDoc processing, report generation — all scheduled and monitored centrally. It reduced manual intervention and weekend support calls significantly. Personally, it helped me move from reactive support to proactive monitoring.
Rock-Solid Stability with Clean Dependency Handling
What do you like best about the product?
What I like most is the stability. Once a job flow is set up correctly, it just runs without daily babysitting. The UI makes it easy to trace failures quickly, and dependency handling is much cleaner compared to older schedulers I’ve used.
What do you dislike about the product?
Some error messages are too generic. When something fails due to an application issue, it takes extra digging to find the exact root cause. Also, initial learning takes time if you’re new to Redwood concepts.
What problems is the product solving and how is that benefiting you?
It solves the problem of manual monitoring and job coordination across systems. Earlier, we had to manually trigger or watch jobs during critical windows. Now, RMJ handles sequencing, retries, and alerts automatically, which reduces on-call stress and production risks.
RunMyJobs Boosts Reliability with Real-Time SLA Dashboards and Instant Alerts
What do you like best about the product?
RunMyJobs has been a catalyst for our transition into a proactive operational model. The combination of real-time SLA dashboards and instant SMS/email alerting serves as our frontline defense; we no longer wait for reports of issues because we are notified the second a job falters. This transparency is the backbone of our system’s reliability
What do you dislike about the product?
We see an opportunity to refine the platform’s diagnostic capabilities. Although the monitoring is robust, the user interface occasionally presents ambiguous error messages that necessitate manual log analysis. Integrating more prescriptive, "instant-read" error summaries would significantly trim our mean time to resolution (MTTR)
What problems is the product solving and how is that benefiting you?
The platform has effectively dismantled our old "firefighting" mentality. By automating status monitoring, we’ve slashed manual intervention by 40%, successfully pivoting our engineering talent away from maintenance and toward strategic innovation
Clear Visibility and Calendar Scheduling Made Month-End Closing Easier
What do you like best about the product?
What I like most is the visibility. Before RMJ, our finance batch processes were a black box. Now I can see job dependencies, SLA risks, and downstream impacts in one place.The calendar-based scheduling also makes month-end closing way less stressful.
What do you dislike about the product?
The learning curve is real. When I first started, the terminology and object structure felt overwhelming. Also, troubleshooting complex workflows sometimes requires digging through multiple layers of logs, which can slow things down if you're new.
What problems is the product solving and how is that benefiting you?
We run overnight financial postings across SAP and several internal systems. Before RMJ, we had manual checks and spreadsheet trackers. Now everything runs automatically with clear dependency control. Month-end close time dropped by almost a full day, and I sleep better knowing failures trigger automatic notifications instead of someone discovering them at 8 AM.
Clear Shift Handovers with Consistent, Predictable Workflows
What do you like best about the product?
What I personally like most is the visibility during shift handovers. When my shift ends, I don’t need to write long explanations. The next person can open the workflow view and immediately understand what has run, what is pending, and what is waiting for a condition. Even when volumes increase, workflows don’t behave unpredictably. It feels consistent and controlled.
What do you dislike about the product?
It requires structured governance. Without disciplined change control, workflows can become complicated over time.Understanding why a job is queued instead of running sometimes requires checking deeper configuration details. It’s not always obvious without experience.
What problems is the product solving and how is that benefiting you?
Before using centralized orchestration, different teams ran scripts independently. If something failed in between, nobody had full visibility. Now dependencies are mapped clearly, and ownership is easier to identify.With centralized orchestration, we can transition infrastructure without losing process integrity. It has made modernization projects much smoother.
Rock-Solid Stability and a Centralized Dashboard That Just Works
What do you like best about the product?
What I like most is the stability. Once jobs are configured correctly, they just run without constant monitoring. It reduced the dependency on manual checks and night calls. The centralized dashboard makes it easier to understand job status across multiple systems instead of logging into different tools.
What do you dislike about the product?
The learning curve is steep, especially for new team members. Simple changes sometimes require deeper product knowledge, and documentation doesn’t always explain real-world scenarios. UI responsiveness could also be improved.
What problems is the product solving and how is that benefiting you?
It solves the problem of fragmented job scheduling across platforms. Earlier, failures were detected late and impacted business SLAs. Now failures are visible immediately, recovery is faster, and operations feel more predictable and controlled.
Rock-Solid Month-End Processing: RunMyJobs Cut Our Monitoring Time by 2–3 Hours Daily
What do you like best about the product?
What I really like about RunMyJobs is the stability during month-end processing. Earlier, we used to monitor SAP jobs manually at midnight. Now RMJ handles dependencies properly and sends alerts only when something actually needs attentionThe UI can feel overwhelming for new users.
It solved our manual job monitoring problem. Earlier, if one job failed, it created a chain reaction and we had to fix it manually. Now, automatic retries and notifications save at least 2–3 hours daily. Personally, it reduced my stress during payroll and financial closing periods.
It solved our manual job monitoring problem. Earlier, if one job failed, it created a chain reaction and we had to fix it manually. Now, automatic retries and notifications save at least 2–3 hours daily. Personally, it reduced my stress during payroll and financial closing periods.
What do you dislike about the product?
I like the centralized visibility. Before RMJ, different teams had their own schedulers. Now everything is visible in one dashboard. The alerting system helps me proactively respond instead of waiting for business users to complain.
It solved coordination issues between infrastructure and application teams. Now we clearly know which job failed and at which stage. This reduced blame shifting between teams and improved overall response time. It improved our SLA compliance noticeably
It solved coordination issues between infrastructure and application teams. Now we clearly know which job failed and at which stage. This reduced blame shifting between teams and improved overall response time. It improved our SLA compliance noticeably
What problems is the product solving and how is that benefiting you?
I appreciate how RunMyJobs integrates with APIs and cloud workloads. We moved some workloads to cloud recently, and RMJ helped automate deployments and batch jobs without major redesign. The flexibility in scheduling based on events instead of just time is a big plus.
Rock-Solid Enterprise Job Scheduling with Execution
What do you like best about the product?
The flexibility stands out for me. You can automate not just simple schedules but complex business workflows. I’ve used it to replace manual steps that people assumed “couldn’t be automated.” Seeing a process run end-to-end without human intervention is very satisfying.
What do you dislike about the product?
Initial design matters a lot. If workflows aren’t planned properly, later changes can be messy. Also, testing complex chains sometimes takes longer than expected.
What problems is the product solving and how is that benefiting you?
It helps eliminate human dependency in repetitive processes. This reduces errors caused by missed steps or delayed execution. For me, it freed up time to focus on improvement work instead of daily execution tasks.
showing 81 - 90