Redwood RunMyJobs Reviews

Redwood Software’s RunMyJobs workload automation solution IT teams can create and run essential scheduled and event-driven processes, manage file and data transfers, and orchestrate automation across applications and other tools like RPA.

Enterprises in every industry, from manufacturing, utility, retail, and biotech to hospitality, banking, and aerospace, rely on Redwood. 

Our low-code automation platform is at the core of critical business operations such as forecasting, replenishment, reconciliation, financial close, order-to-cash, billing, reporting, and more.

Redwood manages the workload of ERP platforms like SAP, Oracle, etc. It also has an additional feature of load balancing through nodes and can restrict the number of jobs running in parallel by entering the execution size limit in the ECC queue.

Redwood manages all complex job workflow processes.

Whenever we are experiencing issues with the Redwood system, we can send log files to the Redwood support team by selecting get support files at the top right corner of the redwood window. Redwood software is supported in almost all web browsers, unlike other software that doesn't support it.

Before, we were using the SAP CPS chronicle tool to schedule batch jobs which doesn't have a user-friendly interface and were not flexible enough to use. Later, when we shifted to Redwood Software everything was hassle-free and we could import hundreds of jobs just using a script. That made our life much easier.

Having multiple options to restrict the use and authority to use Redwood Software to users (user only, scheduler admin, etc) was great. It solved many problems. We can now take reports on how many jobs are running daily, mail alerts for job failures, platform agents connected, and dashboards.

In Redwood, all job-related information can be accessed and downloaded, including job spool lists, job statistics, application logs, etc., which is actually an added advantage for the user to check and analyze the job-related issue.

However, when I check operator messages, there are a lot of messages stuck in the queue. For example, "couldn't send alert" mail to a few recipients. 

The job log has a size limit. 

These are very minor things to look into. If these issues are fixed Redwood, will be in a great position.

The primary use case of Redwood Software in my working environment is that my project includes 24+ applications that are migrated to the cloud as well. We have very complex application flows and integrations. Redwood Workload Automation Edition has helped with application integration. It can integrate with a wide range of applications, including ERP systems, databases, and middleware, which allows organizations to automate end-to-end business processes. 

Also, Redwood has helped in file transfers. It can automate the movement of files between systems, ensuring that data is transferred securely and efficiently. Since our project is also dependent on the cloud, Redwood provides cloud automation which automates the workflows that span across on-premises and cloud environments.

Redwood Workload Automation Edition has helped in improving my organization in numerous ways. 

Our project has complicated workflows and huge tasks to be scheduled. Redwood's features of job scheduling and automation allowed us to schedule and automate batch jobs across multiple platforms and systems, which reduces the manual workload for the employees, saving a lot of time. 

Redwood provides full security while transferring files to different systems. Since ours is a middleware project, the work involves a lot of file movement between different vendors and organizations. By using Redwood, file transfer for the work has been easier and more efficient.

Since my project is a monitoring project, we need to keep an eye on all the applications all the time. The best feature I love about Redwood is the real-time event monitoring and alerting. Redwood can monitor critical business events in real time and can send alerts as well when the predefined thresholds are exceeded. This saves a lot of accountable time for employees and can accurately detect errors with the highest priority, which helps in recognizing and solving the issue within a short span of time. 

Redwood also supports cloud automation to automate workflows between on-premises and the cloud, which is a really cool feature.

The user interface of Redwood can be improved a bit to make it more user-friendly and interesting. Since everything is now updated, it would be better if Redwood's next version release included features involving machine learning and artificial intelligence. 

Since more organizations are migrating to the cloud, it would be beneficial if Redwoood incorporates more cloud-native features such as serverless computing, integration with cloud-native services, and containerization. It would be of added advantage if Redwood could display the workload with visualizations such as flowcharts, bar charts, and process maps which makes the user easy to understand.

I have been using Redwood Software for a period of more than one year.

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 Software is one of the best low-code automation platforms for scheduling complex jobs and monitoring processes. It is used in various domains like banking, manufacturing, hospitality, and so on. It executes critical business tasks such as billing and reporting with high speed and precision which makes it one of the best cloud solutions for organizations.

We can schedule multiple jobs with ease and trigger them as per the requirements. Filters are available for searching and extracting jobs and tracking the error, long-running jobs. The tool is supported by all browsers.

The scheduling of jobs is very complicated, and Redwood makes my task easier as job scheduling is easy in Redwood, and learning modules are simple and clear.

Redwood Software provides some more features like load balancing on nodes, and it is also possible to limit the number of jobs that can run in parallel with the help of an execution size limit in ECC queue.

It is possible to retrieve support files for each of the error, completed, and scheduled jobs which make it easier to find the root cause of a failed job. Redwood software has less coding/scripting with faster performance and delivery of business.

Redwood has multiple job scheduling options; that is, jobs can be scheduled with event wait, they can be chained, and steps can also be added, which makes the user's life much easier.

Installing and configuring Redwood agents are easy, and scheduling jobs on Redwood helps in triggering the batches as per business requirements.

The overall system health and schedule health can be checked in the monitoring dashboard, which shows the total count of errors, completed, and long-event wait jobs so that we don't have to extract reports every now and then for specific issues.

The reports are downloaded in .CAR file format, which makes it difficult to convert to an Excel file. 

The integration with ticketing tools such as ServiceNow takes a lot of time which can be improved.

It would be helpful if we could copy the values from screens especially when we create filters. The job log has a size limit.

They could add additional default time windows and submit frames which would help in scheduling the batch job as per the requirements. 

Redwood will be even better to use if these small changes are looked into, although it's still one of the best tools that we can use for automation.

I've used the soluton for one year.

I build, schedule, and automate jobs. I'm part of the team that did the development and version updates for the tool. Our team generally uses the Scheduler.

Report generation and automated delivery is the primary use case in our project to meet business and management requirements.

Almost all manual tasks and triggers have been replaced with an automated setup.

In terms of implementation, the core of it is SaaS, and we still have some internal servers. It's never 100% SaaS - hence considered a hybrid.

Redwood Software helped me build, deploy, schedule, and set up automated triggers in the jobs. This was a tedious manual activity that had to be automated. That's where Redwood became a life savior.

The monthly and weekly reports were automated as per functional and business requirements. This data was too hard to fetch from the databases. Once Redwood integration was done, this became an easy task.

Redwood Software (Workload Automation Edition) did not help in monitoring and metric generations as continuous monitoring was still required sometimes and we faced some glitches in alerting.

It's an amazing tool. It is flexible and meets almost all functional and business requirements for how you can define jobs and build them. 

There are various ways in which you can construct jobs depending on your business 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.

The monitoring alerts should be set up very precisely for accurate functionality.

The product could be better in terms of its monitoring and alert service. The previous versions have an issue with alert configurations and cannot be properly integrated with the mailing system.

Control systems can be enhanced. We'd like a role-based module so that the users, administrators, and super users can have elevated/differentiated access based on their roles.

The metrics explorer is yet to be enhanced so that the statistics can be made available easier for better user interaction and analysis. This could enhance visibility and Interaction.

I've used the solution for one year.

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 use this for scheduling SAP batch jobs.

The jobs can be scheduled as per the requirements.

We can easily import jobs from SAP ECC systems.

As it has pre-defined options and it helps in managing the jobs.

We can connect to many third-party systems.

There won't be a memory outage issue, as it uses its own server/ECC memory only.

Without any interruptions, Redwood can connect to N number of third-party systems/legacy systems. There won't be any interruption to the job.

With an easy search option, we can get details about jobs.

We can schedule a batch job for all third-party systems and help to schedule jobs as per the regional/country time.

The alerting mechanism prevents business impact, and we have no need to log in to the SAP system and monitor batch jobs. Whenever any job fails/is long-running we immediately get an email notification and we can take necessary action.

It offers easy scheduling of jobs daily/weekly/monthly.

There are many filters we can use to check the job status. There is also a customized filter option which helps to get the reports as needed. 

As this contains almost all the time zones, we can schedule jobs as per the regional/country time.

The best part of the tool is the submit frame & time window where we can schedule jobs as per the requirements.

We can schedule a batch job for all third-party systems.

This tool supports all browsers.

As it includes alerting mechanisms, it helps to avoid some business impact.

Without any interruptions, Redwood can connect to N number of third-party/legacy systems. Once the job is scheduled, there won't be any interruption to the job.

We need the automatic creation of incidents for failed jobs.

In the dashboard, it could show the total count of jobs in a system, for example,  how many are in running/scheduled/held/event wait states.

In reports, if we have pre-defined reports such as killed/completed jobs of that particular month, it would be easy for auditing purposes.

If there's a direct export option, it would be great. Every time we need to run a report to export the data.

Submit frame/time window could have more pre-defined options, which will help us to schedule the job easily.

It's been a year of using this tool.

We did not use a different solution previously.

It is cost effective.

License renewal is a very easy process.

We did not evaluate other options.

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.