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.
RunMyJobs Brings Reliable, Centralized Visibility to Daily Operations
What do you like best about the product?
What stands out the most for me is the reliability and visibility it brings to daily operations. Before using it, a lot of our scheduling and dependency handling felt scattered across scripts and manual monitoring. With RunMyJobs, everything is centralized, and I can clearly see job flows, failures, and retries without digging through multiple systems.
I also appreciate how stable the platform feels in production. Once workflows are configured correctly, they tend to run consistently without constant babysitting. This has reduced late-night incident calls and given our team more confidence in automated processes.
I also appreciate how stable the platform feels in production. Once workflows are configured correctly, they tend to run consistently without constant babysitting. This has reduced late-night incident calls and given our team more confidence in automated processes.
What do you dislike about the product?
One challenge I’ve faced is that the initial learning curve is quite steep, especially if you’re new to Redwood’s terminology and workflow design approach. Documentation exists, but in real scenarios you still end up relying on trial-and-error or internal knowledge sharing.
The UI, while functional, doesn’t always feel intuitive for quick troubleshooting. Some common actions take more clicks than expected, and filtering large job lists could be smoother.
I’ve also noticed that making structural changes to existing workflows requires careful planning, because even small updates can impact downstream dependencies if not handled properly.
The UI, while functional, doesn’t always feel intuitive for quick troubleshooting. Some common actions take more clicks than expected, and filtering large job lists could be smoother.
I’ve also noticed that making structural changes to existing workflows requires careful planning, because even small updates can impact downstream dependencies if not handled properly.
What problems is the product solving and how is that benefiting you?
End-to-end orchestration across multiple systems
Automatic failure handling and alerts, reducing manual monitoring
Clear audit trails, which help during incident reviews and compliance checks
Automatic failure handling and alerts, reducing manual monitoring
Clear audit trails, which help during incident reviews and compliance checks
Reliable Workflows and a Centralized Dashboard You Can Trust
What do you like best about the product?
What I genuinely like is the reliability. Once a workflow is set up correctly, it just runs without me constantly checking logs. I can finally trust that overnight and weekend jobs won’t break silently. The centralized dashboard also makes it easy to see dependencies instead of jumping between multiple tools.
What do you dislike about the product?
Initial setup takes effort. If you’re coming from traditional schedulers, the learning curve feels a bit steep in the beginning. Some error messages could be more descriptive for faster troubleshooting.
What problems is the product solving and how is that benefiting you?
Earlier, job failures were discovered only after business users complained. Now, failures are detected early and handled automatically. This has reduced firefighting, improved SLA adherence, and honestly lowered stress during on-call rotations.
Reliable Automation That Reduces Daily Operational Noise
What do you like best about the product?
What I like most about RunMyJobs is the sense of control it gives over complex automation without making things feel overly technical. It handles cross-system job dependencies smoothly, which reduces a lot of manual follow-ups and uncertainty during critical processes. The platform is reliable in the background—once workflows are set up, they just run as expected, allowing teams to focus more on outcomes rather than constantly monitoring executions. I also appreciate how it brings visibility to issues early, making troubleshooting more proactive than reactive.
If you want, I can make this shorter, more technical, or more business-focused depending on where you’re posting it.
If you want, I can make this shorter, more technical, or more business-focused depending on where you’re posting it.
What do you dislike about the product?
One drawback is that some advanced features are not very intuitive at first and require time to fully understand, especially for users who are new to enterprise automation tools. Certain configurations feel more complex than necessary, and small changes can sometimes involve multiple steps. Additionally, reporting and dashboards could be more flexible, as extracting highly customized insights is not always straightforward without extra effort.
If you want this to sound softer, more critical, or more technical, tell me the tone you need.
If you want this to sound softer, more critical, or more technical, tell me the tone you need.
What problems is the product solving and how is that benefiting you?
RunMyJobs solves the core challenge of reliably managing, scheduling, and automating complex IT workflows across different systems and platforms. Before using it, coordinating multiple jobs across databases, servers, and applications meant lots of manual checks, ad-hoc scripts, and firefighting when things didn’t run in order. RunMyJobs removes that uncertainty by providing a central orchestration layer, so tasks run in the right sequence, with clear dependencies, alerts, and logging.
The benefit to me is consistency and peace of mind. Workflows that used to require manual oversight now execute automatically with fewer failures, and when something does go wrong, the platform highlights it quickly so I can fix the real issue instead of spending hours tracking it down. That translates into reliable operations, more time for strategic work, and fewer late-night emergency fixes.
The benefit to me is consistency and peace of mind. Workflows that used to require manual oversight now execute automatically with fewer failures, and when something does go wrong, the platform highlights it quickly so I can fix the real issue instead of spending hours tracking it down. That translates into reliable operations, more time for strategic work, and fewer late-night emergency fixes.
RMJ’s Unified Control Layer Enables Cleaner, Scalable Architecture
What do you like best about the product?
RMJ stands out to me because it shifts orchestration out of individual applications and into a unified control layer, eliminating repetitive logic and enabling cleaner architecture with built-in scalability.
What do you dislike about the product?
RMJ offers strong capabilities, but it requires a learning phase, and resolving issues can occasionally depend on admin intervention rather than being entirely user-driven.
What problems is the product solving and how is that benefiting you?
RMJ eliminates ad-hoc recovery scripts by embedding contingency handling and alerts directly into a governed workflow model, turning patchwork logic into a streamlined, centrally managed process.
RunMyJobs Shifts Us from Ad‑Hoc Requests to Workflow Design according to department
What do you like best about the product?
RunMyJobs has quietly changed the way people request work. In the past, business users would ask, Can you run this tonight? Now the question is more often, Can we model this as a workflow? That move away from ad-hoc execution toward process thinking has also changed how IT is perceived. We’ve gone from being operators who just run tasks to being designers of the flow.
What do you dislike about the product?
In the past, when something failed, we could chalk it up to complexity or the system being unpredictable. These days, though, failures are usually down to configuration mistakes or logic issues.
What problems is the product solving and how is that benefiting you?
It cleared up the organizational fog. I can now trace responsibility and ownership of the workflow across departments. That added clarity has strengthened executive reporting and cut down on pin pointing.
On a personal level, it’s also made performance conversations much easier, because decisions are supported by execution data rather than opinions.
On a personal level, it’s also made performance conversations much easier, because decisions are supported by execution data rather than opinions.
Centralized Workflow Orchestration with Real-Time Visibility—RunMyJobs Delivers
What do you like best about the product?
RunMyJobs gives me a centralized way to orchestrate complex workflows across multiple systems. The cloud-native design means I don’t have to worry about infrastructure maintenance, and the dashboards provide visibility into job status in real time. I especially appreciate the flexibility to integrate with SAP and non-SAP applications seamlessly.
What do you dislike about the product?
The initial learning curve was steeper than expected. While the interface is clean, some advanced features require digging into documentation or support calls. Also, reporting customization could be more intuitive.
What problems is the product solving and how is that benefiting you?
Before RMJ, we had fragmented scheduling tools across departments, leading to missed dependencies and manual interventions. Now, jobs run reliably overnight, freeing my team from babysitting batch processes. This has reduced downtime and improved SLA compliance, which directly impacts customer satisfaction.
RunMyJobs Makes Month-End Workflow Prototyping Fast and Reliable
What do you like best about the product?
What I like best about RunMyJobs: The fully web-based UI with visual workflow builders and native parallel processing lets me prototype month-end chains (e.g., GL extracts → validations → reports) in under an hour, backed by SaaS-grade 99.99% uptime and global runner pools that absorb spikes without provisioning servers.
What do you dislike about the product?
Concepts like workload partitions (for segregating prod/test traffic) have a steep curve with sparse onboarding docs, and exporting granular histories (e.g., every rerun event) often needs custom API calls or support tickets rather than one-click exports
What problems is the product solving and how is that benefiting you?
We battled fragmented dependencies—no central alerting meant overnight failures went unnoticed until morning chaos, derailing audits. RMJ unifies it all with event-driven alerts, conditional branching, and full traceability, automating 80% of repetitive interventions; this boosts reporting accuracy, shaves days off close processes, and builds stakeholder confidence through reliable, transparent operations in a high-stakes financial environment.
Live SLA Tracking and Real-Time Alerts Transformed Our Workflow
What do you like best about the product?
One of the most transformative improvements for us has been the introduction of live SLA tracking, paired with automated SMS and email alerts. Having real-time visibility into job progress and potential delays has completely changed the way we operate. Rather than relying on assumptions or waiting for issues to surface, we now get immediate insight that lets us step in proactively when something starts to slip. Overall, it’s moved us from a reactive mode to a truly action-driven workflow, and it has noticeably improved both our efficiency and the quality of service we deliver.
What do you dislike about the product?
The end‑to‑end transparency delivered by the live monitoring dashboards is truly exceptional. Having instant alerts the moment a schedule starts to slip has completely transformed how quickly we’re able to respond. What used to require manual checks or delayed follow‑ups is now surfaced in real time, allowing us to course‑correct immediately and maintain far tighter control over service performance.
What problems is the product solving and how is that benefiting you?
The level of visibility we have now is truly unparalleled. With SMS alerts triggered the moment an SLA window is missed, we’re always the first to know—not the last. This proactive awareness has significantly sped up our operational response and reinforced overall service reliability. Review collected by and hosted on G2.com.
Automated Scheduled Jobs That Cut Manual Work
What do you like best about the product?
Automatically runs scheduled jobs (daily reports, billing, payroll, backups, etc.)
Reduces manual work
Reduces manual work
What do you dislike about the product?
Pricing is generally suitable for large enterprises
Not affordable for small businesses
Not affordable for small businesses
What problems is the product solving and how is that benefiting you?
One platform to control all jobs across systems.Automatically retries failed jobs and sends alerts.Dashboard shows what’s running, failed, or completed.
Predictable Workflows That Take the Stress Out of Month-End Closing
What do you like best about the product?
What I personally like most is how predictable everything becomes once workflows are built properly. Earlier, month-end closing used to be stressful because someone always had to manually monitor jobs at odd hours.I also appreciate how role-based access control lets me give limited access to support teams without risking system changes.
What do you dislike about the product?
UI-wise, I feel some areas could be more intuitive. For new team members, understanding where logs and execution history are stored takes time. Also, exporting reports could be smoother.Documentation is decent, but certain edge cases require deeper guidance.
What problems is the product solving and how is that benefiting you?
We previously depended on cron jobs scattered across servers. That created version control issues and no centralized logging. With RMJ, everything is traceable. Debugging is faster because logs are consolidated. Personally, it made deployments less risky and more auditable.The biggest benefit for me is reduced firefighting — I spend more time planning instead of reacting.
showing 31 - 40