The platform is very user-friendly, making both implementation and migration straightforward. It also simplifies the automation of various processes, whether they involve SAP, non-SAP batch jobs, or finance-related tasks. We offer 24/7 customer support, including a separate Technical Account Manager. We are currently using this product for SAP, Informatica, Informatica Cloud, PeopleSoft, Power BI, and Tableau; it has made our day-to-day operations very smooth and easy. We are using this like our everything. Review collected by and hosted on G2.com.

The AI component is somewhat slower compared to other automation tools. Review collected by and hosted on G2.com.

I like that I stopped thinking in terms of “servers” and started thinking in terms of “process flow.” Earlier I spent more time checking whether agents were alive than actually improving automation.

The dependency visualization helped me explain complex job chains to non-technical managers that unexpectedly reduced a lot of blame during failures.

The restart options are granular enough that I don’t need to rerun an entire nightly batch when only one branch failed. Review collected by and hosted on G2.com.

Debugging sometimes feels like reading a story backwards logs are detailed but not always arranged in the order I mentally expect.

Small UI delays when switching between job history and definitions can interrupt troubleshooting rhythm.

Permission layers are powerful but occasionally too strict, which slows urgent fixes. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

What I like most about RunMyJobs is the level of reliability and control it gives over enterprise job orchestration, especially in complex environments. In my experience, once a process is modeled and stabilized in RMJ, it just runs — day after day — with very minimal operational noise. Compared to legacy schedulers we used earlier, RMJ significantly reduced midnight failures and manual interventions. Review collected by and hosted on G2.com.

The biggest challenge with RunMyJobs is the initial learning curve. It’s not a tool that feels intuitive on day one, especially for teams coming from traditional schedulers like Control-M or cron-based systems. Concepts like process definitions, events, and advanced dependencies require proper training to use effectively.

Another area that could improve is error messaging and troubleshooting. When a job fails, the error shown in RMJ is sometimes too generic, forcing us to dig into logs at the OS or application level. For junior team members, this can slow down incident resolution. Review collected by and hosted on G2.com.

What changed for me personally is the predictability of the night shift. Earlier I had to keep multiple job monitors open and still got surprise failures at 3 AM. With RMJ, the event-based chains and the way dependencies are visualized let me understand the entire flow in one place. I also like that I can restart from the exact failed step without re-running the whole process — that alone saved us hours during month-end The biggest win for me is coordinating file arrivals, API triggers, and warehouse loads without writing glue scripts. Earlier our team maintained custom schedulers in Python just to manage timing and retries. Now the orchestration is visible to both the ops and data teams, so there’s less “whose pipeline failed confusion. Review collected by and hosted on G2.com.

During month-end close, the sequence of tasks is everything. I like that I can see a business-process view instead of just technical job names. I don’t need to call the technical team to ask “has the reconciliation started?” — I can see the stage myself. Review collected by and hosted on G2.com.

I've been using RunMyJobs for about a year now, and I gotta say, it's been a game-changer for our workload automation. What I like best about it is how it simplifies job scheduling and monitoring across our hybrid environment. I can easily see and manage jobs across different systems, which has reduced errors and saved me a ton of time. The predictive analytics feature is also super helpful - it alerts me to potential issues before they happen, so I can proactively fix them. Review collected by and hosted on G2.com.

What I dislike about RunMyJobs is that the initial setup was a bit complex, and it took some time to get used to the interface. But once I got the hang of it, it's been smooth sailing. Also, sometimes the reporting feature can be a bit slow, but it's not a major issue. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.