Skip to main content
TrustRadius
Redwood RunMyJobs

Redwood RunMyJobs

Overview

What is Redwood RunMyJobs?

Redwood Business Process Automation is a workload automation and job scheduling solution designed for and delivered via Software-as-a-Service (SaaS). It transforms the digital enterprise with scalability and integration with all technologies in the modern enterprise. Redwood unifies workflows across on-premises, private, hybrid and public…

Read more
Recent Reviews

TrustRadius Insights

Redwood Workload Automation, also known as RunMyJobs, is a powerful tool that provides a centralized platform for scheduling and …
Continue reading

Flexible Software

9 out of 10
April 06, 2023
Redwood is so flexible, we can monitor all business process automation jobs from different system. Scheduling also very easy jobs can run …
Continue reading

Associate Consultant Perspective

10 out of 10
March 30, 2023
Hi, We use redwood workload automation for scheduling jobs and for automatic alerts generation in case of long running and failed jobs. It …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 6 features
  • Multi-platform scheduling (21)
    9.6
    96%
  • Central monitoring (21)
    9.4
    94%
  • Alerts and notifications (21)
    9.4
    94%
  • Logging (21)
    9.4
    94%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Redwood RunMyJobs?

Redwood Business Process Automation is a workload automation and job scheduling solution designed for and delivered via Software-as-a-Service (SaaS). It transforms the digital enterprise with scalability and integration with all technologies in the modern enterprise. Redwood unifies workflows…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

21 people also want pricing

Alternatives Pricing

N/A
Unavailable
What is Control-M?

Control-M from BMC is a platform for integrating, automating, and orchestrating application and data workflows in production across complex hybrid technology ecosystems. It provides deep operational capabilities, delivering speed, scale, security, and governance.

What is PagerDuty?

PagerDuty is an IT alert and incident management application from the company of the same name in San Francisco.

Return to navigation

Features

Workload Automation

Workload automation tools manage event-based scheduling and resource management across a wide variety of applications, databases and architectures

9.4
Avg 8.2
Return to navigation

Product Details

What is Redwood RunMyJobs?

Redwood Business Process Automation is a workload automation and job scheduling solution designed for and delivered via Software-as-a-Service (SaaS). It transforms the digital enterprise with scalability and integration with all technologies in the modern enterprise. Redwood unifies workflows across on-premises, private, hybrid and public cloud environments. It bridges gaps in complex processes that function between mainframe, distributed, virtual and cloud resources. Clients use Redwood to create intelligent process flows that support diverse IT processes for business including managed file transfer, hybrid cloud automation, complex data management, and DevOps. Redwood enables people to focus on innovation instead of daily management of repeated processes.

Redwood RunMyJobs Screenshots

Screenshot of Dashboard users see when first logging in.Screenshot of Shows a specific process definition, how a user would edit that definition.Screenshot of Built in testing environment to run the definition without leaving the definitionScreenshot of Editing a whole process chain, not just a single processScreenshot of Shows the Process Monitor where we can see the status of the chain execution, this instance is with an errorScreenshot of Shows the Process Monitor where we can see the status of the chain execution, this instance is without an errorScreenshot of Dashboard that tracks high level aggregate oriented metrics, such as total errors,etc.Screenshot of This is a visual dashboard that shows various process metrics

Redwood RunMyJobs Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported CountriesGlobal
Supported LanguagesEnglish, Dutch, German, French, Arabic, Bulgarian, Catalan, Danish, Greek, Estonian, Finnish, Hebrew, Hungarian, Italian, Japanese, Korean, Lithuania, Dutch, Norwegian, Polish, Portuguese, Romanian, Russian, Slovak, Slovenian, Spanish, Serbian, Swedish, Thai, Turkish, Ukrainian, Vietnamese, Chinese

Frequently Asked Questions

Control-M, CA Workload Automation, and IBM Workload Automation are common alternatives for Redwood RunMyJobs.

Reviewers rate Multi-platform scheduling and Analysis and visualization highest, with a score of 9.6.

The most common users of Redwood RunMyJobs are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(32)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Redwood Workload Automation, also known as RunMyJobs, is a powerful tool that provides a centralized platform for scheduling and automating business processes across multiple platforms. Before implementing RunMyJobs, companies faced challenges with fragmented scheduling systems that lacked visibility and alerting capabilities. However, by using Redwood Workload Automation, organizations can now schedule cross-platform processes with confidence, ensuring that prerequisites are completed successfully and on time.

Large corporations have found great value in using Redwood Workload Automation to streamline their operations. It offers a user-friendly interface that eliminates the need for coding or scripting, making it accessible to a wide range of users. The ability to integrate with various programs and platforms further enhances its versatility. Redwood Workload Automation has become the go-to solution for automating financial transactions, report generation, batch processing, file transfers, and more.

The benefits of Redwood Workload Automation extend beyond automation itself. It provides centralized control and support for on-premises, hybrid, and pure cloud environments. This means that businesses can manage their tasks and jobs from different systems in one unified location. Moreover, Redwood Workload Automation supports load balancing and process priorities across multiple applications, enabling companies to optimize resource usage and reduce costs.

Overall, Redwood Workload Automation has received positive feedback from users who appreciate its ease of use, excellent customer support, and the ability to simplify complex workflows. It has proven to be a valuable tool for automating tasks and processes on multiple platforms while increasing efficiency and productivity for businesses of all sizes.

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
RunMyJobs is being used across all of IT to provide a centralized point of processing, monitoring, and alerting for our business processes running on Windows Servers, AS/400 (iSeries), and Linux platforms, as well as direct JDBC connections to databases. Before implementation, processes were scheduled in various independent areas, such as windows task scheduler, with no alerting and no visibility for an operations team to monitor. In addition, before RMJ, cross-platform processes just had to be scheduled in good faith that prerequisites finished on time and successfully. RMJ solves that issue as well.
  • Upgrades are fast and can be done in a "lights-out" manner
  • The ability to organize functions into applications is very helpful
  • Events such as a file watcher to kick off a process when a file is detected are done very well
  • The documentation is lacking severely, many times even leading to a suggestion of paying for professional services to figure out processes. Also not updating documentation when a new release makes the old documentation obsolete.
  • AS400/iSeries has been a constant battle since inception, once an update fixes one thing, another seems to break within the AS400/iSeries space, and sometimes the fixes don't actually fix the issue. Over time now this has gotten much beter.
  • Allowing an issue to go back and forth within a ticket countless times (sometimes over 40 responses) without just getting everyone together on a meeting. Update - this has gotten much better with time.
  • Communication needs a lot of improvement. I have had to reach out to support just to get release notes when a new release is made available.
  • The ability to get accurate counts of historical process runs is limited currently to 35 days and since you are billed for each process run in all environments, not just Production, this limits accountability in historical billing inquiries.
Since we are not an SAP shop, which I know the RunMyJobs company has, it seems like it's hit and miss, where I think maybe an SAP shop might have less issues. AS400/iSeries is touch and go. We have a lot of SSIS package runs and some complicated chains, file watchers that kick off events, and even are able to kick off scheduled jobs in ServiceNow.
  • Automation
  • Scalability
  • Alerting
Workload Automation (6)
56.66666666666667%
5.7
Multi-platform scheduling
70%
7.0
Central monitoring
70%
7.0
Logging
20%
2.0
Alerts and notifications
80%
8.0
Analysis and visualization
70%
7.0
Application integration
30%
3.0
  • An issue occurred when we ran out of "credits" much sooner than anticipated. Further investigation showed a process in a TEST environment that was scheduled to run every 15 minutes was accidentally submitted on a schedule twice (so 2 processes running every 15 minutes). At that time we didn't even have the ability to run a report to find the rogue process, the vendor had to run it for us. That lack of ability for the customer was one thing, but to be dinged for non-production is also a point of contention.
  • Positively for the processes that report correctly, it has been a big benefit for our IT Operations team to have the centralized monitoring of our critical processes.
  • The ability to have a centralized system for our operations team to monitor and receive alerts has been very beneficial.
I was not part of the decision making on choosing RunMyJobs, but my understanding on what made RMJ stand out was the fact that it is in the cloud, with no infrastructure support needed on our side, as well as a promise that you could schedule and monitor jobs within ServiceNow. We later found out the ServiceNow promise was not correct and still don't have a direct method as of this writing.
ServiceNow IT Service Management, Redwood Reporting : Report2Web, SAP BPC (Business Planning and Consolidation)
20
Data Warehouse, Application Development, IT Operations, Server Engineering, Application Support
3
It helps to have a broad understanding of IT functions for how we use runmyjobs, for instance, I know how to reboot a windows server via command line (although google will tell you as well), then to call an SSIS package on a SQL server, run a batch file, etc... With just that broad knowledge it makes it easier to understand the processes you have to support in the product. From there it is just repetition in the various aspects, such as the calendar functions, alerting, events, etc...
  • Process Automation
  • Monitoring
  • Alerting
  • Centralization
  • Create ServiceNow incidents for the owning teams when a process fails.
  • Schedule reboots for troublesome servers.
  • Execute ServiceNow scheduled jobs via RMJ.
  • Hopefully SFTP.
Being in the cloud is a big help, with less hardware to maintain, the patches and updates are fast and easily done, we have built a good working relationship with Redwood.
No
  • Price
  • Product Features
  • Product Usability
Being a redwood customer certainly helped, as well as the price for an enterprise scheduler in the cloud.
I think it would have been nice to have had some time to work through the tool, but I was trained while we were trying to implement, so it would be nice to have more time to get an overall understanding of the product before being live, but it all worked out.
  • Third-party professional services
Redwood assisted in the implementation
No
It seems many pressing issues have to be escalated to their dev team, which I believe is mostly overseas. The response time isn't always the greatest. I go back to the documentation as well, if that was better there would be less need of support from myself. There are also times when they figure out the resolution, it has to be included with a fix in which you have to wait for the next release, however long that may be. Update - the support response time and quality of answers has greatly increased in the past 6 months or more.
I'm unaware of the premium support.
No
I think there is a lot of functionality in this product, and even more that my company could probably benefit from, but not easy to decipher without better documentation or other avenues of exposure. Aside from some bugs here and there, we have been able to integrate SQL processes, SSIS packages, file events, do SOAP calls into ServiceNow (although we don't have true verification if the job completes successfully), create alert emails that email ServiceNow to create incidents for process failures, and many more things, all without actually scheduling our ERP system processes (ran on AS400) in RunMyJobs.
  • File Watcher events
  • Alerts for processes in certain states (error state mostly)
  • Process chains that involve multiple steps
  • The promotion of multiple objects from one environment to another can be a little cumbersome one at a time.
  • Acknowledging multiple operator messages, if not from the same process can be a bit cumbersome.
No
Return to navigation