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.
Game-Changing Real-Time Alerts and SLA Dashboards
What do you like best about the product?
The Best Part: The real-time alerting and SLA dashboards provide total visibility. Knowing the second a job misses its window via SMS/Email is a game-changer.
What do you dislike about the product?
Error reporting in the UI is sometimes too vague. We’d love to see more specific diagnostic data upfront to avoid manual log digging.
What problems is the product solving and how is that benefiting you?
We’ve cut "firefighting" and manual checks by over 40%, moving from a manual morning routine to a fully automated, exception-based model.
Game-Changing Real-Time Alerts and SLA Dashboards
What do you like best about the product?
The real-time alerting (SMS/Email) and SLA dashboards are game-changers. They provide a perfect balance between granular, immediate notifications and high-level health overviews.
What do you dislike about the product?
The UI-level error reporting is sometimes too vague. Enhancing the platform with more descriptive initial error messages would save us the time currently spent digging through logs to diagnose root causes.
What problems is the product solving and how is that benefiting you?
Since implementation, we’ve cut manual monitoring and firefighting by 40%, moving away from tedious morning status checks to a fully automated, exception-based model.
Proactive Monitoring with Indispensable Alerts and SLA Dashboards
What do you like best about the product?
RunMyJobs excels in its proactive monitoring capabilities. The alerting system and SLA dashboards are indispensable; receiving immediate notifications via email and SMS allows us to respond to job failures or window misses instantly, while the visual dashboards keep us informed on overall system health.
What do you dislike about the product?
Streamlining the diagnostic process would be a significant win. Currently, error messages can be somewhat ambiguous, requiring deep log dives to find a resolution. Integrating more descriptive, "at-a-glance" error summaries directly into the UI would greatly accelerate our troubleshooting.
What problems is the product solving and how is that benefiting you?
RMJ has transformed our workflow from reactive to proactive. By eliminating manual status checks, we have successfully reclaimed over 40% of our manual intervention time, allowing the team to focus on higher-value tasks rather than "firefighting."
Standout Alerting and SLA Dashboards with Instant Email/SMS Notifications
What do you like best about the product?
The alerting system and SLA dashboards are standout features. Instant notifications via email and SMS ensure we’re alerted the moment a job fails or misses its window, while the dashboard provides a high-level view of system health.
What do you dislike about the product?
The error reporting can occasionally be vague. We often have to dive deep into the logs to diagnose the root cause; having more descriptive, "at-a-glance" error messages within the UI would streamline the troubleshooting process.
What problems is the product solving and how is that benefiting you?
Before RMJ, our mornings were consumed by manual status checks. By automating these monitors and shifting us to a proactive alerting model, we’ve reduced our "firefighting" and manual intervention time by more than 40%.
RMJ Delivers Confidence and Accuracy in Every Payroll Cycle
What do you like best about the product?
What I like most is the confidence it gives during payroll cycles. Payroll processing has zero tolerance for mistakes, and RMJ ensures that calculations, validations, and bank file generations happen in the correct order.The dependency control prevents reports from running before transaction updates are complete.
What do you dislike about the product?
Understanding complex dependency trees can be difficult if you didn’t design them yourself. When inheriting workflows from another team member, it takes time to fully understand the structure.It rewards disciplined configuration.
What problems is the product solving and how is that benefiting you?
It solved report inconsistency caused by premature job execution. With proper dependency management, our reports now reflect finalized data, which has improved decision-making reliability.That reduced transition risks and shortened project timelines.
Structured Control for SAP Background Processing—Clear Dependencies, External Execution
What do you like best about the product?
What I like most is how it gives structured control over SAP background processing without hardcoding logic inside SAP itself. I can manage dependencies, set conditional checks, and control execution externally.It reduces confusion about when something actually runs.
What do you dislike about the product?
Sometimes when jobs are held due to a condition, the reason isn’t immediately obvious to junior team members. It requires understanding how the workflow was originally designed. It’s powerful, but not always self-explanatory.It works well technically, but visual clarity could improve.
What problems is the product solving and how is that benefiting you?
It solved cross-region coordination issues. Previously, tasks were triggered manually by teams in different time zones, leading to delays. RMJ centralized that activity, improving compliance and reducing operational risk.It solved inconsistent report generation. Earlier, reports sometimes ran before data loads completed.
Powerful Control Over ERP Job Chains with Flexible, Script-Free Workflow Adjustments
What do you like best about the product?
What I appreciate most is the level of control it gives over complex ERP background jobs. Once I properly define job chains and conditions, I don’t need to constantly monitor them.I like how workflows can be adjusted without rewriting scripts. It acts as a control layer instead of embedding logic inside applications.
What do you dislike about the product?
The structure is powerful but not very forgiving. If you misconfigure a dependency, it’s not always obvious until something doesn’t trigger as expected. It requires careful design upfront.Some waiting conditions are not visually obvious. You need to understand the workflow deeply to quickly identify why something hasn’t started yet.
What problems is the product solving and how is that benefiting you?
It solved the issue of unpredictable job execution in our ERP environment. Earlier, jobs depended heavily on manual timing and coordination. Now execution is structured and automated,This has reduced operational confusion and improved reliability.
Rock-Solid Stability for High-Volume, Complex Workflows
What do you like best about the product?
What I like most is the stability. Once workflows are properly built, they just run. We process thousands of jobs across SAP, cloud apps, and internal systems daily, and I don’t have to constantly babysit them.
I also appreciate how it handles complex dependencies without becoming messy.
I also appreciate how it handles complex dependencies without becoming messy.
What do you dislike about the product?
The learning curve is real. For someone new, especially junior admins, it can feel overwhelming at first. The UI is powerful but not always intuitive. Also, building advanced workflows sometimes requires deeper knowledge than expected — it’s not always as “drag-and-drop simple” as it looks.
What problems is the product solving and how is that benefiting you?
Before RMJ, we had manual interventions for overnight batch jobs, and failures were often discovered hours later. Now, processes are automated end-to-end, including alerts and retries. It has reduced operational risk, cut overtime hours, and improved SLA compliance. It basically turned reactive firefighting into proactive monitoring.
RMJ Instant Transparency into Business-Critical Workflows
What do you like best about the product?
I’m not a technical person, so what I value most is transparency. I can log in and immediately see whether our business-critical workflows are on track, without needing someone else to interpret the information for me.
What do you dislike about the product?
The interface feels like it’s geared more toward technical users. At times, I wish it offered simpler, business-level views by default, so it would be easier to get the key information without having to dig through more technical details.
What problems is the product solving and how is that benefiting you?
Our order processing and reporting tasks used to rely heavily on specific individuals remembering to trigger each step. RMJ replaced those manual checkpoints with automated flows, which reduced delays and made our operations far more predictable,especially during high-volume periods.
Rock-Solid Orchestration for Quarter-End and Year-End Cycles
What do you like best about the product?
What stands out for me is how confidently it handles high-pressure cycles like quarter-end and year-end. We run long job streams that depend on multiple validations, and once the workflow is structured, it behaves exactly as designed.For example, I can trigger downstream processing only after specific upstream system conditions are satisfied. That orchestration capability has removed a lot of timing guesswork
What do you dislike about the product?
Understanding object relationships in the beginning was difficult. The logic behind certain configurations isn’t immediately obvious,Some failure messages are too technical and require deeper system knowledge to interpret. It would help if the tool provided clearer business-level explanations by default.
What problems is the product solving and how is that benefiting you?
It addressed the lack of control in automated processes. Previously, scheduling decisions were scattered and poorly documented.It solved fragmented monitoring. Before, I had to log into multiple servers to check cron jobs and scripts. Now execution status is centralized.
showing 111 - 120