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

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

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

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

If I could change one thing, it would be the surface-level error reporting in the console and it is user friendly.When something breaks, I’d love for the UI to tell me why right away, rather than just telling me that it broke, which would save me from digging through the raw logs Review collected by and hosted on G2.com.

The diagnostic layer in the web interface is a bit thin. We often find ourselves performing "log forensics" to get to the root cause of an issue and it is getting hung sometimes. Making those initial error messages more descriptive would be a massive time-saver for our developers Review collected by and hosted on G2.com.

I really like how robust the SAP scheduling in RunMyJobs is. It works perfectly to schedule jobs across multiple regions and time zones. It easily manages multiple dependencies and resolves various business issues like jobs running in multiple systems with interdependencies, as well as handling time zone and factory calendar restrictions. Additionally, it's a SaaS solution with good services, which means less headache on our side and an overall better solution through Redwood. The initial setup was very good. Review collected by and hosted on G2.com.

RunMyJobs does not have a complex search tool yet. An inbuilt tool to search and extract data based on complex criteria would be helpful. Also, the cleanup process sometimes does not work properly and might need optimization. Review collected by and hosted on G2.com.

As a data engineer, I like that RunMyJobs lets me orchestrate complex ETL and ELT pipelines across databases, data lakes, and cloud services from a single platform. The visual workflows, rule‑based scheduling, and reusable job templates make it easy to standardize data pipelines and keep them reliable as they scale. Review collected by and hosted on G2.com.

When you start building very large DAG‑style workflows, some configuration screens can feel crowded and it takes time to organize objects and naming conventions well. Advanced tuning of SLAs, calendars, and exception handling also requires a bit of experimentation before it fits each data pipeline perfectly. Review collected by and hosted on G2.com.

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

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

What I genuinely like is how stable it feels once everything is configured correctly. We run a lot of SAP background jobs overnight, and earlier we had random failures that needed manual follow-up. With RunMyJobs, I feel more confident leaving things unattended because the dependency handling is very precise. The logging is detailed enough that I don’t need to SSH into systems unless absolutely necessary. It saves time during incidents. Review collected by and hosted on G2.com.

Learning curve is real. Documentation is detailed but not always practical.Sometimes small changes require formal deployment processes, which slows down quick fixes. For business users, it’s not very intuitive without technical support. Review collected by and hosted on G2.com.

I use RunMyJobs to automate my routine tasks and workflows, which helps me schedule and run jobs automatically without having to manage them manually. It helps me avoid repetitive tasks and makes sure the scheduled jobs run on time, reducing the chances of error. I like how it makes automation very easy and reliable. It's also easy to use and monitor jobs. Additionally, it integrates well with our internal tools to automate and manage scheduled jobs. Review collected by and hosted on G2.com.

Sometimes the interface feels a little complex when you are new to the platform. Review collected by and hosted on G2.com.

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

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

Its scalability shines in orchestrating massive chains—think 25+ data sources (SAP, Oracle DBs, APIs) linked via drag-and-drop flows with parallel execution, auto-scaling runners, and seamless integrations that handle terabytes without choking, all managed from a browser anywhere. Review collected by and hosted on G2.com.

The credit-based consumption model can surprise you during dev/testing phases (a single rogue infinite loop ate 20% of our monthly quota once), and advanced scripting for partitions or custom plugins requires SQL/JCL fluency, which isn't plug-and-play for generalists. Review collected by and hosted on G2.com.