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.
RMJ’s API-First Extensibility Transformed Our Batch Processing
What do you like best about the product?
The dependency visualization actually reduced my stress — I can see upstream and downstream jobs clearly before touching anything.
I like that I can trigger emergency reruns without waiting for another team.
The audit trail helps during post-incident reviews; it saves me from guessing what happened at 2 AM.
I like that I can trigger emergency reruns without waiting for another team.
The audit trail helps during post-incident reviews; it saves me from guessing what happened at 2 AM.
What do you dislike about the product?
Sometimes the interface feels too technical for new team members; onboarding takes time.
Error messages are detailed but not always beginner-friendly.
I wish there were smarter suggestions when a workflow fails.
Error messages are detailed but not always beginner-friendly.
I wish there were smarter suggestions when a workflow fails.
What problems is the product solving and how is that benefiting you?
Solved frequent overnight batch failures that required manual monitoring.
Reduced escalation calls because alerts are more structured.
Helped standardize automation across multiple environments instead of custom scripts everywhere.
Reduced escalation calls because alerts are more structured.
Helped standardize automation across multiple environments instead of custom scripts everywhere.
Dependencies That Just Work—Overnight Chains Run Smoothly in RunMyJobs
What do you like best about the product?
I like how it connects different applications without needing custom glue everywhere. It gives our operations team a single place to manage workflows.
What do you dislike about the product?
Some small configuration tasks also require digging through documentation or trial-and-error.
What problems is the product solving and how is that benefiting you?
RunMyJobs solved that by centralizing scheduling and making dependencies explicit. Now the team spends less time checking logs and more time improving the workflows themselves.
Low-Code Templates Make Process Automation Easy
What do you like best about the product?
Users can design process with minimal programming using pre built templates and low code interface making automation accessible beyond it team
What do you dislike about the product?
Not beginners friendly, user may need training to fully understand work flow and automation
What problems is the product solving and how is that benefiting you?
RunMy Jobs solves the problem of manual, repeated, time based business task and replace them with automated, reliable
Clear Impact Visibility That Speeds Up Incident Resolution
What do you like best about the product?
When there is a failure, I can see upstream and downstream impact clearly. It helps me resolve incidents faster without going through multiple teams.I like how scalable it is.
What do you dislike about the product?
The reporting customization is not very intuitive. If I want very specific audit-level reporting, I sometimes need support from technical teams.It tells you that a job failed, but not always the root cause immediately.
What problems is the product solving and how is that benefiting you?
Now scheduling is standardized, which reduced error rates and improved system stability.It solved our overnight batch dependency issues.
Reliable All-in-One Management with Strong Alerting and Planning Tools
What do you like best about the product?
The audit trail is especially helpful during month-end closing. The alerting mechanism is proactive rather than reactive. What I like most is how it reduced our dependency on one “scheduler expert.” Earlier, only one team member understood the job chains deeply.
What do you dislike about the product?
Documentation examples could be more scenario-based. It’s powerful, but that power requires structured thinking.
What problems is the product solving and how is that benefiting you?
It reduced reconciliation delays and helped us close books almost a day earlier than before. Now it’s automated end-to-end. It reduced operational firefighting and improved delivery accuracy.
Reliable End-to-End Automation with Strong Enterprise Control
What do you like best about the product?
What I like best about RunMyJobs by Redwood is how effortlessly it centralizes and automates complex business processes without the usual infrastructure overhead. Being fully SaaS, there’s no need to manage servers, upgrades, or patches everything just runs reliably in the background.
It’s especially strong in enterprise environments, with seamless orchestration across ERP systems, cloud applications, databases, and file transfers. The visual workflow design makes it easy to build and monitor processes, while still offering the depth and control needed for complex automation scenarios.
Overall, it reduces operational effort, increases visibility, and gives confidence that critical business processes will run on time, every time.
It’s especially strong in enterprise environments, with seamless orchestration across ERP systems, cloud applications, databases, and file transfers. The visual workflow design makes it easy to build and monitor processes, while still offering the depth and control needed for complex automation scenarios.
Overall, it reduces operational effort, increases visibility, and gives confidence that critical business processes will run on time, every time.
What do you dislike about the product?
One drawback of RunMyJobs by Redwood is that its depth and enterprise focus can make it feel complex at first. The learning curve can be steep, especially for teams that are new to workload automation or coming from simpler schedulers.
Because it’s a SaaS platform, customization and deep troubleshooting sometimes depend on vendor support, which can slow things down if you’re used to having full on-prem control. Advanced configurations and integrations may also require specialized knowledge, particularly in large SAP-heavy environments.
Additionally, pricing may feel high for smaller organizations that don’t need enterprise-scale automation, making it more suitable for mid-to-large enterprises rather than small teams.
Because it’s a SaaS platform, customization and deep troubleshooting sometimes depend on vendor support, which can slow things down if you’re used to having full on-prem control. Advanced configurations and integrations may also require specialized knowledge, particularly in large SAP-heavy environments.
Additionally, pricing may feel high for smaller organizations that don’t need enterprise-scale automation, making it more suitable for mid-to-large enterprises rather than small teams.
What problems is the product solving and how is that benefiting you?
RunMyJobs by Redwood solves the problem of fragmented and manual workload management across multiple systems. Before using it, managing job scheduling and monitoring across ERP systems, databases, and other applications required significant manual oversight and multiple tools.
With RunMyJobs, we’ve been able to centralize and automate complex workflows in one platform. It handles dependencies, retries, alerts, and monitoring automatically, which has significantly reduced manual intervention and operational risk.
The biggest benefit has been improved reliability and visibility. Critical processes run on schedule with clear monitoring and audit trails, and when issues occur, they are easier and faster to resolve. Overall, it has streamlined operations, reduced workload on the team, and increased confidence in our automation processes.
With RunMyJobs, we’ve been able to centralize and automate complex workflows in one platform. It handles dependencies, retries, alerts, and monitoring automatically, which has significantly reduced manual intervention and operational risk.
The biggest benefit has been improved reliability and visibility. Critical processes run on schedule with clear monitoring and audit trails, and when issues occur, they are easier and faster to resolve. Overall, it has streamlined operations, reduced workload on the team, and increased confidence in our automation processes.
End-to-End Job Chain Visibility with Meaningful Alerts and Faster Morning Checks
What do you like best about the product?
What I personally like most is the way cross-system job chains are visualized. Earlier, I had to check SAP, SFTP transfers, and data warehouse loads separately. Now I can see the full dependency flow in one place and quickly identify where something is stuck without logging into five different tools. The alerting is also meaningful — it tells me which step failed and why, not just that a job turned red Our biggest issue earlier was overnight batch uncertainty. We used to manually check whether finance postings, IDoc processing, and file loads completed. Now everything is event-driven, and I only get involved if there’s an exception. It has reduced our morning validation time from about 1.5 hours to 15 minutes.
What do you dislike about the product?
The REST and scripting capability helped us standardize orchestration for non-SAP workloads. We trigger cloud data pipelines, run Python scripts, and wait for file arrivals using the same scheduler. I like that I can build reusable job definitions instead of cloning and modifying hundreds of similar jobs We had cron jobs scattered across servers with no central visibility. When something failed, nobody knew until a business user reported missing data. Now failures are detected immediately and auto-recovery steps run before we even get a ticket. It has improved our SLA compliance significantly.
What problems is the product solving and how is that benefiting you?
For support, the run-time log detail is the biggest win. I don’t need to ask the development team what a job was supposed to do — I can see parameters, predecessor jobs, and output directly. The rerun options with different start points are very practical during incident handling From a functional side, I like the predictability. Our period-end activities (allocations, reports, reconciliations) start automatically based on real completion of upstream tasks, not fixed timings. It removed the need for us to send “please start now” emails to IT.
RunMyJobs Streamlined Our Workload Automation and Monitoring
What do you like best about the product?
RunMyJobs has really improved how we manage and automate our workloads. The interface is user-friendly, and setting up complex workflows feels structured and straightforward. Monitoring is much easier compared to traditional schedulers, and alerts help us respond quickly when something goes wrong. Overall, RunMyJobs has increased efficiency, reduced operational overhead, and given us better control over our scheduling processes.
What do you dislike about the product?
RunMyJobs is a strong automation tool, but the learning curve can be steep at the beginning. When I started, navigating through dashboards and locating specific job details wasn’t very straightforward. Some features are not immediately obvious, so it takes time and practice to use the platform confidently. While it offers powerful capabilities, new users may need proper guidance and hands-on experience to get fully comfortable with it.
What problems is the product solving and how is that benefiting you?
RunMyJobs has helped us move away from reactive support to a more proactive approach. In the past, missed or delayed jobs often created confusion across teams, and we had to manually verify execution statuses. With RunMyJobs, real-time monitoring and notifications give us immediate insight into what’s happening. It has minimized unexpected issues, improved cross-team coordination, and brought greater transparency and accountability to our processes.
Intelligent Waiting and Easy Reruns Keep Our Cross-System Workflows Running Smoothly
What do you like best about the product?
What made the biggest difference for me is the way cross-system jobs wait intelligently instead of failing. Our store sales upload used to break if the SFTP file was late by even a minute. Now the workflow just pauses and continues when the file arrives. I also like the quick rerun option with the same parameters — it saves a lot of time during business hours We no longer have to manually track whether 300+ store files are processed. That alone removed a full daily checklist. The morning sales report is ready before the business logs in, which improved trust in IT support.
What do you dislike about the product?
The time-zone handling is something I didn’t expect to appreciate this much. We have plants in three regions, and earlier we maintained separate schedules. Now it’s one workflow with local execution timing. Also, the ability to restart from the exact failed step instead of the whole chain is a huge productivity boost Production order integration used to be monitored manually by the planning team. Now they only get notified when something actually needs attention. It reduced unnecessary calls to IT and let planners focus on shortages instead of job status.
What problems is the product solving and how is that benefiting you?
The audit trail is extremely detailed. During internal reviews, we can show exactly when a critical job started, which variant was used, and who approved the change. That level of traceability was not available in our old scheduler During our migration project, we used it as an orchestration layer rather than just a scheduler. We could trigger data loads, validation scripts, and reconciliation reports in one pipeline. The parameter sets for each migration wave were very easy to reuse
RMJ Made Month-End Processing Predictable and Stress-Free
What do you like best about the product?
I like how predictable month-end processing has become. Earlier, I used to sit and wait for multiple reports to finish before moving to the next step. Now everything flows automatically, and I just review the outcomes. It feels like RMJ turned a stressful ritual into a checklist.
What do you dislike about the product?
Sometimes it’s hard to explain to non-technical stakeholders why a job is delayed. RMJ gives technical details, but translating them into simple business language takes effort. I wish there were more “business-friendly” status summaries.
What problems is the product solving and how is that benefiting you?
It solved the issue of timing gaps between departments. Finance, HR, and IT used to run tasks independently. Now, RMJ ensures my finance report runs only after HR data sync is complete. That removed mismatches that used to show up days later in reconciliations.
showing 11 - 20