Redwood RunMyJobs Reviews

My responsibilities include a number of monotonous manual tasks to be done on a day-to-day basis like data validation, data cleansing, proofreading, data uploads, database maintenance, scheduling DB jobs, monitoring success and error reports, creating relationship models between multiple data sets, etc.

These tasks take most of my time, and I end up working outside of office hours and even on weekends, even after putting in so much manual effort I used to end up making errors and spending hours debugging and starting from scratch many times.

Redwood RunMyJobs has automated all of the manual jobs into a simplified automation process. It has taken care of scheduling, DB jobs, monitoring the jobs, and generating reports that can help me in analyzing data and provide better insights into the business.

Redwood has eliminated the effort of coding, building, deploying, and maintaining an efficient automation platform. It manages automation upgrades and eliminates dependencies, redwood enables you to automate business processes end-to-end and manage them seamlessly.

The most valuable aspects include:

1) Effortless nature. Eliminates the effort to host, deploy and maintain the automation platform.

2) Fully managed. Manages automation upgrades and eliminates dependencies.

3) Powerful. Uses modern design to avoid outdated scheduling limitations.

4) Future Proof. It can centralize and support on-premises, hybrid, and cloud environments seamlessly.

5) Support and Service. We have been quite impressed and positive about the 24/7 support service offered by Redwood; they're always there to assist whenever there is a need. We like that, every time, someone from the Redwood support team just resolves the issue like a genie.

Improvements include:

1) Cost of the Software. Redwood is more expensive than most of the other Automation Software available today; they could make it budget-friendly.

2) It has limited reporting features. Some basic reporting features are missing.

3) There is no option to extract data in Excel. This feature could help in finding errors in the data.

4) Integration with ServiceNow is not supported.

5) The cloud platform compatibility is not up to the mark.

6) Security standards need to be improved.

7) Handling failure is not great; the workflow stops when a job fails and human intervention is required.

8) Configuration and set-up are difficult for someone with less coding knowledge.

9) They need to provide more documentation to assist new users.

I've used the solution for less than a year.

It is a stable solution; a great feature that will keep it stable is the 24/7 support and assistance.

The automation can definitely reach a wide user base due to the fact its future-ready and ability to integrate with other applications and platforms. 

I have reached out to customer service and support many times including late night hours. The support team was so responsive and resolved issues in less time as they are very proficient and experienced in troubleshooting.

Positive

We previously used Microsoft SharePoint. It still required more manual intervention and was not as completely automated as Redwood.

The initial setup is simple if you possess intermediate coding skills and someone who is a beginner might feel it is a bit complex.

We implemented the solution in-house.

The product has saved a lot of time and manual effort with high accuracy and reliability.

The set-up cost is high and could be priced lower for smaller organizations.

We did not evaluate other options.

It is a great automation solution with minor cons and I am sure it will get better.

1. Our project has been integrated with multiple technologies like SAP and non-SAP, HANA cloud, and others. Redwood helped us to automate all the tasks, jobs, workflows, and events.

2. It has a provision to showcase job statistics at a single UI called dashboards.

3. Low resource utilization and effective monitoring.

4. Low-cost software compared with other scheduling applications.

5. Easy to add external dependencies among the jobs in the workflows and automate as per the business requirements.

The solution has improved the organization by:

1. Automating a large number of jobs and workflows across all technologies in a single place.

2. Integrating with ServiceNow for auto-creating Incidents in case of any job failures.

3. No manual monitoring of batch jobs.

4. Offering a high-security standard application and low-cost software.

5. Having advanced features like dashboards, logging, and load balancer.

6. Reducing resource utilization and automating all external dependent jobs.

7. Different security functionality for restricting users to certain functions (read/write).

The most valuable aspects of the solution are:

1. The ability to schedule tasks and jobs on multiple platforms (SAP and Non-SAP) and monitor the jobs.

2. Its ability to organize, monitor, control, and schedule all jobs and activities.

3. Redwood is a more powerful tool and provision to automate any tasks/jobs than any other tool in Batch scheduling (automatic and other tools).

4. It has advanced features like dashboards where users can see all statistics.

5. It has an alert mechanism feature; if any job fails, it triggers notifications.

6. Different security functionality for restricting users to certain functions (read/write).

7. Cost Reduction, complete automation, optimized resource usage, and full audit trail.

8. Vendor support.

9. Logging and statistics.

The improvements that can be made on the solution include:

1. They need to update/add more value-added features and functionalities in the upcoming releases.

2. The solution should have more focus on security standards.

3. Making connectivity/agent setups with multiple technologies should be easier and must be one step installation.

4. They should add more UI for easy usability of the Redwood application.

5. Sometimes, there are false alerts in the case of job failures.

6. It would be great if users could access this on external devices.

We have been using Redwood for our client for more than three years.

The client/project required one-step automation for scheduling and monitoring a large number of jobs and is able to connect to any kind of environment (Unix, Windows and etc).

The initial setup was straightforward. 

Redwood is low-cost software compared with other scheduling applications and is recommended.

We looked into Automic - UC4

Redwood is a centralized management system for batch jobs in SAP EP7. Jobs can be planned in Redwood in the most effective way possible with a number of job-related activities, such as the ability to restart, resubmit, kill, cancel, edit, hold, release, and enable/disable the scheduled work with a single click. 

A single click can stop, start, hold, release, activate, or disable anything in the Redwood system. Instead of stopping the process server until there is a serious problem, you can stop the specific queues where the jobs have been affected or are having problems.

Recently, we modified our Redwood RunMyJobs employment schedules. Redwood was used to scheduling about 2000 jobs; its benefit is that it allows us to connect to databases and obtain information; in the past, we had to create numerous jobs and files to carry out this process. 

REL expressions are quite helpful for setting up the preconditions.

To load the data and output the reports to the business, there are many different process chains that are active. It would be quite impossible to manage the flow of data burden without redwood. Redwood, in this case, manages all data loads. It is impossible to manage such complicated architecture and flow of data manually. Redwood Run My Job, a fantastic automation tool, is appreciated.

There are 389 or more scheduled jobs from Redwood, some of which will have a significant influence on the firm (high, medium, and low-priority jobs based on their business impact). Eventually, leads determined that tickets should be raised automatically on the ServiceNow interface and incidents should only be created for high-priority tasks. I discovered a priority level while working on this particular requirement. We can set the priority level to 90+ or the highest for high-priority jobs and in-process alert sources using the rules tab. Then, we can set the variable as priority and operation equal to or in range, and we can set the value to 100. Thus, SNOW will automatically raise an incident when a high-priority job fails.

Once I had solid hands-on experience with the software, it wasn't tough for me to learn this application. Everything was easy and flawless. The only issue at first was that we had to manually delete or raise the event in order to run some of the events and wait for jobs, even if the file was kept at the correct AL11 position. 

Eventually, after contacting the Redwood support team, we were able to resolve this problem. We experience sporadic connection failures while executing jobs in other systems, such as AS400, and after the work is finished at the AS400 end, the Redwood system keeps attempting to get the status from the AS400 system. 

This attempt cannot be manually controlled. We could set up a system where, after a certain amount of time, the job would be abandoned if the server hadn't responded.

I've used the solution for one to two years.

I'd rate the stability nine out of ten.

I'd rate the solution ten out of ten.

Technical support is always helpful.

Positive

I did not use a different solution previously.

The initial setup is straightforward.

I'd rate the vendor team ten out of ten.

I'd rate the ROI ten out of ten.

I did not evaluate other options.

It's used for all of our SAP applications. We have ERP, CRM, and data warehousing. It's used for our PeopleSoft, and it's used for some of the other corporate internal applications. Informatica Data Warehousing uses it.

I don't build jobs. I'm part of the team that did the version and the infrastructure part of it. Our teams go through the process definition and the chain definition for the most part, and I believe they do not use the visual process editor.

In terms of deployment, the core of it is SaaS, and you still have some internal servers. It's never 100% SaaS.

Going to a SaaS solution has eliminated some of the down times that we needed to install some of our patches. For our agent servers, we're able to create redundant servers so that we can take one down at a time and not involve any downtime. So far, the various upgrades that we received had extremely short outage durations of one or two minutes. The ability to stay up-to-date and current, both from a security standpoint and from an application enhancement standpoint or bug fixes, has been fabulous as compared to an on-prem solution, which would take a long project to upgrade. That's probably been the biggest benefit. Moving to a SaaS solution has a lot of advantages. When you're running factories and projects 24 hours a day and seven days a week, uptime is very important, and you try to minimize any downtime, even planned downtime.

It has dramatically reduced the time and effort that our organization spends on deployment, updates, and maintenance. With our other application, it would be a six-month project to do a major upgrade. So far, with the upgrades that have been done by Redwood, the downtime is only for a few minutes. There is a gigantic difference.

We're pretty heavy into SAP. They have a good SAP interface where we're able to create and utilize jobs even from SAP, which gives us some additional features. It's about the same on the other applications that are simply running command-type batch jobs, but the SAP interface gives us a lot of flexibility. Some of it's similar to what we already had, but it has a positive impact on us.

It's a very powerful tool. It has a lot of flexibility for how you can define jobs and build them. There are different ways in which you can construct jobs depending on your specific needs and requirements. It has a lot of features for different ways that you can build jobs, which is great for power users but a bit confusing for newcomers because there are a lot of different options. 

It lacks some of the common reporting features. I'm a bit surprised that there aren't some standard reports to be able to extract any data on usage. They've described to us that customers have different reporting needs, so they let them develop those, but reporting is a common need. It would be helpful to have it as part of the solution.

One of our business groups has used Redwood SAP BPA for at least 10 years before I started working with it, and then the rest of our teams moved over from AutoSys to Redwood over the last year and a half.

It has been pretty stable. Performance-wise, we've had to work on it a bit simply because of our volume. That's more with database performance. We haven't had any problems with any jobs because of any bandwidth performance.

So far, it's been good. It scales. As we did the conversion, we did probably eight different deployments or eight different sub-projects to bring various applications live. That part of it scaled very well, with the exception of some of the performance of the database tuning, which took some time, but part of it had to do with the high volume of jobs that we run.

It's deployed across a broad list of applications, across multiple data centers. Its users include business people, developers, and schedulers for jobs. There are hundreds of people who use it.

I have contacted them. I would rate them an eight out of ten at this point.

Positive

Over the last year and a half, we've migrated from AutoSys to Redwood. We switched because of their roadmap and their commitment to keeping the product fresh by patching on a regular basis and providing regular updates. Looking at other competitors, there was also the cost-benefit.

The future of AutoSys was unclear. It was a product that we had used for almost 25 years, but the roadmap was unclear on whether that was going to be a viable product going forward. It put us onto a SaaS product that is definitely more stable and gives us a roadmap into the future for enterprise-wide job scheduling.

Redwood is a little more complex than the AutoSys application we used before. It creates some challenges from the standpoint that there's a two-step process. You build a job and then you schedule the process to run. You build a process definition or a chain definition, whereas, in AutoSys, you do it basically in one step. That part has been a little bit more difficult, but it has given us a lot more flexibility, specifically in terms of the ability to write some very complex calendaring that we couldn't quite do before for the scheduling portion of it.

It was complex. We had a high number of jobs, and we had a percentage of jobs that were very complex in terms of how they were built. Also, we were moving from a system that had been in place for over 20 years. So, you don't always have experts around who understood why it was done that way, but the conversion pretty much brought everything over the way it was executed before.

We spent a year. Part of that was the volume of jobs that we have and the number of teams involved. We've got multiple job scheduling teams by application. We don't have one central team, which made it more difficult from a conversion standpoint. There were a lot of people to train.

As a job scheduling tool, Redwood has reduced the footprint for what's needed. There are still process servers that are required to be inside in order to communicate with SAP and keep the communication inside, which is good from a security standpoint, but the core application is in the cloud. So, we're not responsible for patching the database or patching the core components of the application. This means our upgrades have become very simple because it's a small agent that gets updated during any software release. So, the actual upgrade process is just a few minutes of downtime, which has been a huge benefit. Server-wise, we probably have the same number of internal servers because there are some gateway servers that are utilized, and we've duplicated them and made them redundant so that we can take down and patch them one at a time to minimize any downtime and failover capabilities. Our net is probably similar, but the planned downtime is significantly or exponentially less.

Being hosted on SaaS has reduced the patching requirements that are needed. Any of the connectivity and vulnerability requirements are pretty much handled by the application now, so we don't have to deal with that internally. When you move to a SaaS solution, you're at the wind of the internet, if you will, for final connectivity, but it's not quite as important in job scheduling because your jobs, once they fire off and run, continue to run on the application servers if there is any outage. So, it's not like other applications that are more chatty or require a persistent connection.

We used the Redwood migration team. Our experience with them was good. They are sharp people, and they know their product very well. Alex Borders was the most helpful. He was our lead for the conversion. He had a huge wealth of knowledge.

From our side, there were two of us who worked on it from a standpoint. I worked on it from the technical side, and the other person worked on it from the governance side in terms of whatever we had to change internally process-wise, but each application had its own teams involved in it. So, there were hundreds of people involved in it. Most of it was from the testing and training standpoint for the job support and job processing teams, basically our developers and schedulers.

We're not even a full year into running it yet, so it's a little hard to provide any input about the ROI.

It initially surprised me because we went from an application that was priced by connection to agents/the number of agents to an application that was priced based on the number of job executions. At that time, many of the products we looked at were also priced on job execution. That seems to be more common in the business or in the vendors that provide solutions out there, but that was probably our biggest difference.

An evaluation of other products was done, but we had already used the SAP version of Redwood. So, we were already familiar with its capability. The fact that we already had people who were familiar with supporting it weighed pretty heavily into it.

It's important to do a PoC, take some of your complicated processes, and ensure that your expectations are met.

For the people I work with, the time freed up from using this solution is about the same because we were already using an Enterprise job scheduler. It's probably the same workload. Similarly, the reduction in service interruptions and process failures is the same, but we've drastically cut down our planned downtime. 

I would rate it a nine out of ten.

Redwood RunMyJobs is mainly used to make job schedules happen automatically. I've used it for important tasks, and it's been really helpful. It's a dependable and efficient platform for automating important work processes. 

You can also use it to automatically back up your organization's data every day. It shows how well your organization is doing and tells you if something important doesn't work. Redwood RunMyJobs has saved me a lot of time and effort because it does my job schedules automatically. 

I would recommend it to anyone who needs a good tool for getting work done on time. One great thing about it is that it's good at handling errors and can work with other systems. It's easy to set up if you know a bit about it, and it's user-friendly. It helps you get more done.

Redwood RunMyJobs made my organization work better. It saves us a lot of time and money by doing jobs automatically. It also reduces the mistakes that people make. 

The tool is really good at keeping our data safe when it's being used. We can connect it to other systems and programs easily. It also tells us how well our work is going and helps us find and fix mistakes. 

Redwood RunMyJobs is a tool we can trust. Redwood makes things happen automatically and smoothly. It helps make the process of creating and using software easier, so we can deliver it faster. This means we can keep testing and using it all the time. This saves time, makes our software better, and lets us control how we build it.

This solution is like a reliable alarm system. 

It sends alerts right on time, telling everyone when a task is about to fail because it's taking too long or when it's stuck unexpectedly for a while. 

It also lets everyone know when a job is successfully done, making it easy to keep track of our work. It's a super useful tool for doing repetitive tasks, and it saves a ton of time while making sure mistakes are rare. 

When we need to stop all scheduled tasks, especially during updates or downtime, we can pause them easily.

It would be nice if Redwood RunMyJobs could work on different systems. 

The support team is helpful, however, they could be even better at reaching out to users who need help. 

If the reporting options were more flexible, it would make the product better. 

Also, if the way it looks and works is easier for people who don't know much about tech, that would be good. 

We're impressed with the way Redwood transformed workflow automation in our organization. It has become an integral part of our daily and weekly operations, streamlining processes, and increasing efficiency. Redwood has a great Interface that is easy to use. Even with limited technical knowledge, one can make configurations in it. Scheduling the batch jobs, automating the data transfers and complex workflows are fully automated, and no manual intervention is required. It seamlessly integrates with other systems to bring the solution.

Using Redwood has enhanced efficiency like never before, It has pre-built templates and libraries, which makes it easy to design and customize the workflows the way we require. It brings comprehensive solutions to our automation in an organization. 

Monitoring and alerting is the best feature. We can be notified of the status of the task. Error handling is an advanced feature that increases the accuracy of the work. Redwood is more flexible and we can schedule the tasks based on different time zones.

Compared to the features of other automation tools, Redwood has many advanced functionalities in it. The initial setup and configuration of Redwood are straightforward. It takes little time to become familiar with all the features, including drag-and-drop functionality. Some templates make it relatively easy to use. Its scheduling capabilities help ensure tasks are accurately executed on time. We can identify the issues and address them quickly. Reports are generated by the filters and scheduled timings to track the status of the tasks.

I would appreciate it if they improved the service in terms of support and assistance for the software. There is a lack of resources and product documentation which, if included, would help to gain more knowledge about the application. 

Small businesses may step back from the solution as the cost and pricing are more expensive. 

The downtime of the software should be reduced; it takes quite a long time to download the bulk data. 

The Excel document export option is unavailable for job transport.

Redwood is primarily used for DevOps automation in our business for agile, functional application delivery. 

It helps in creating logical workflows from the data center to the cloud with automation. Redwood easily manages and coordinates complex processes and automates their interdependencies without manual intervention which is an impressive feature. 

Every step is fully logged and auditable at a process level, without manual intervention. It can visually combine workflow steps into the process chains.

Redwood has helped in automating the scheduled tasks and jobs. 

We can create and test micro-workflows to find defects sooner. Redwood helps in eliminating repetitive and time-consuming manual steps for better productivity. 

The tool is very compatible with multiple CI/CD tools. Every step is fully logged and auditable at a process level, without manual intervention. It can visually combine workflow steps into the process chains. 

It enforces consistent business and IT service standards across the enterprise without extra manual effort.

Redwood Software has many excellent features, including, automating any number of tasks without lagging, and provides multi-tier environments like development, test, and production. 

It has an event-driven automation feature for accurate, complete data and faster results. 

Built-in SLA monitoring allows you to meet your SLA targets and get early warnings for deadline breaches. 

We can create and test micro-workflows to find defects sooner. 

Redwood helps in eliminating repetitive and time-consuming manual steps for better productivity. The tool is very compatible with multiple CI/CD tools.

Redwood Software has a high price tag, especially for small and medium-sized businesses that might not have the funds to engage in a complete automation system. 

The initial setup of the software is quite challenging. There are some difficulties faced during dependencies set up under jobs. 

The customer support and documentation part can be improved for much better response and understanding. A course could be provided on the tool in the market about the importance and usage. 

Apart from the above, Redwood is doing great at its automation and is highly recommended

 I've used the solution for two years.

We did not previously use a different solution.

We did not previously evaluate other options.

RunMyJobs has been used in our security project. 

We have a security monitoring tool that would trigger alerts for the pre-defined conditions, and RunMyJobs would send a request to the integrated ITSM. That way, automatically incidents are created with the data populated from the triggered alert. The associate can then investigate the triggered alert and report incidents.  

This has reduced the manual work for associates and has provided more time and concentrate on the critical business task.

This solution has cut down on the manual work the associates need to perform to create incidents for the triggered alerts and as well as eliminate the scope of error and also provides associates more time to concentrate on investigation and also other critical business tasks.

The associates are also able to get the status of the process through the dashboard which has most of the critical data needed to know on the process. This is faster and more efficient as it is integrated for incidents. It allows the team to meet the SLA defined by the customer.

RunMyJobs can be easily integrated with other software to perform automation. Our team was able to integrate it with the ITSM tool as well as security monitoring tools to make the incident creation process automatically feasible. 

Rather than going through a number of documentation and support calls, an individual can easily implement the tool and also provide knowledge transfer to the team members. 

The dashboard provided can be made more visually appealing and could include more critical data that would help associates in one glance get the required information.

There can be more pre-built integration setups that can be used based on the changing business requirements. Due to the lack of this, we are forced to integrate adapters. Not all third-party tools are easily integrated into the Redwood RunMyJobs for automation purposes. 

I've used the solution for less than a year.

This is a good automation tool to implement if a company wants something to perform repetitive tasks that need to be done on a daily, monthly, or quarterly basis. 

It's a very scalable product and can take on large workloads.

We did not use any tool previous to this.

We are able to cut down the time it takes to manually handle tasks.

I'd advise others to have a detailed call with support to understand the integration.

We looked into Tidal Workload Automation.

Basically, this tool is primarily used due to the fact that it is very reliable for every new user. We can say that it is a user-friendly tool. 

Redwood Workload Automation is really a great product. Personally, I would recommend it to every enterprise as a workflow/process automation tool.

As a new user, it is easy to connect with any application, including SAP ABAP, Oracle, and Peoplesoft. Redwood provides many good searches as well (i.e. fuzzy, wildcard, etc.)

In Redwood, we can easily create jobs and easily transport them from one environment to another. There are multiple tabs available as per the client's requirements. You can easily schedule and monitor the jobs.

Earlier, my organization was using the Automic UC4 tool for scheduling purposes. However, there were many cons to using it - like more coding and script knowledge required. In contrast, in Redwood, we can easily create the job and it's very interactive for the user.

In Redwood Workload Automation, we can schedule many jobs at the same time using different time zones. In this way we can easily create the notification part, alerting and monitoring as per the user's needs.

This tool provides many quick functions in your system screen, including refresh, running queues, process servers, and filters.

The most valuable feature of this tool is the fact we can easily check a notification or alert on our mobile phones. We don't need to open our system at all.

In Redwood Automation, we can easily fetch the daily reports from the system as per the client's requirement and track the status of every job which is running, aborted, or canceled.

It provides us with strong server security and load balancing. Redwood Automation helps to cover logging and debugging.

Overall, these features definitely reduce the time-consuming processes, which improves the business processes as well. 

There are fewer cons in Redwood as compared to other tools available in the market. That said, it would be a great thing if they would provide a few new features, like a health dashboard and a few time frames, which could help with more scheduling of jobs in a convenient way.

We'd like to see an integration with ServiceNow to raise the tickets/incidents in ServiceNow.

Apart from this, I don't have any negative points related to this tool. It has already overcome the cons and is doing a fantastic job in the automation field. It's one of the best and most used tools in the market.

I have been using Redwood for more than one year, and it has been a great experience with them so far.

The product provides good stability when it comes to delivering jobs. We can easily match the client's requirements as an output. The system queue, server, alerting, and configuration all play vital roles, and they perform well.

It is really very scalable.

Everything is perfect with the support team. They delivered their service very well.

Positive

Before Redwood I used Automic UC4. However, there are a few cons to that solution. For example, for a new user, it is very difficult to interact with the UI. Also, creating or scheduling any jobs required script knowledge.

It is a little bit hard to start the initial step. However, after that, everything goes smoothly.

The product provides good ROI for the businesses, and our client was really very happy with the live system.

As compared to Control-M and UC4, the setup cost and pricing of Redwood are far less as they are delivering good functionality at this price point.

I did not evaluate other options. I choose the Redwood tool without any doubt since I used it personally. I suggested to everyone that it was a very reliable and easy-to-use tool.

Everything is perfect in this tool.

Redwood is very easy for functional users to learn and use. The steps are useful and therefore end user training is easy to deliver.

It is a high-performance, secure, stable, and scalable platform.

Redwood is a great solution to complement and enhance our SAP instance. 

Redwood has good flexibility in automating our own processes using the plug-and-play components from their big library store. One of the most beneficial parts of RunMyJobs is we don't have to support and maintain the infrastructure for the scheduler; it's all in the cloud, so Redwood takes care of that maintenance and upkeep.

Redwood automation helps us to rely on the software to get our core business processes run on time with almost no expected errors. This is time effective, which helps us to meet the client's requirements

A whole lot of jobs can be controlled with just one click, which is time effective. We can control a complex workflow with simple events, which makes life easier

Redwood is of value to our organization due to of its ease of use and the ability to automate and orchestrate any platform that we utilize today. 

Redwood has pre-defined process definitions, a data transformer, a chain diagram of the process, and error handlers.

When something obstructs the job flow, instead of scheduling and running a new job, we can set up tasks in a logical flow that runs automatically during job failures. 

The best thing about the Redwood software's RunMyJobs is it has automated jobs running smoothly with no issues, and automated upgrades are completed in less than five minutes. This makes maintenance very easy.

Redwood software helps to integrate complex processes in a heterogeneous landscape that combines SaaS and on-premise solutions.

Currently, our developers aren't able to access their own objects in the user acceptance testing server and production system server as they are assigned the developer access role, which is kind of a solid role, and no changes or additions can be made to it. In the next release, I would suggest that the access can be limited but accessible by developers

Also, in terms of an outage, this becomes critical since it tasks some time to identify and restore our services with which we fail to reach our Service level agreements.

We highly recommend the product overall.