ActiveBatch by Redwood Reviews

I have been familiar with ActiveBatch by Redwood for a while now and have had exposure to it through workflows involving automation and ETL processes. Since a lot of my work has involved integrating APIs, scheduling reporting tasks, and automating pipelines, I have worked with similar workload automation concepts over the past year or so.

My main use case for ActiveBatch by Redwood is automating and scheduling workflows, especially around data pipelines and reporting processes. For example, during my analytics work, we had workflows where data was pulled from multiple APIs, processed, and then pushed into dashboards or reports. A tool like ActiveBatch helps automate the entire sequence instead of just running everything manually, so rather than someone checking and triggering jobs individually, this platform can schedule tasks, monitor dependencies, and ensure that everything runs in the right order.

ActiveBatch by Redwood helps connect different parts of the workflow together. For example, a process might start with pulling data from APIs, then running transformation scripts in Python or SQL, followed by updating dashboards or reports. Instead of treating those as separate manual steps, ActiveBatch by Redwood helps create a more centralized and automated workflow. This is really useful for me because a lot of my projects involve recurring reports and ETL tasks, so reducing manual intervention saves a lot of time and avoids errors.

The best features ActiveBatch by Redwood offers, in my experience, are mainly around job scheduling, workflow automation, and monitoring. I especially appreciate the ability to automate recurring workflows and track dependencies between tasks. That is helpful when I am working with data pipelines where one process depends on another finishing successfully. I also find the monitoring and alerting features useful because they make it easier to quickly identify any failed jobs or workflow issues instead of manually checking everything. Overall, I mostly use it for improving reliability and reducing repetitive operational work.

After using ActiveBatch by Redwood, one specific outcome that I noticed was around reducing manual effort and improving workflow readability. For example, in workflows tied to reporting and ETL processes, automation helped reduce the amount of manual monitoring and repetitive execution significantly. Automating the scheduled data workflows and integrations helped improve analyst productivity by around 25 to 30%, mainly because less time was spent manually triggering jobs or fixing missed dependencies. Another improvement was around consistency, where scheduled workflows ran on time with fewer operational errors, speeding up the reporting turnaround and reducing delays in downstream tasks. Overall, the biggest impact was really around time saving, operational efficiency, and more reliable execution of recurring workflows.

To improve ActiveBatch by Redwood, the UI could be more modern and intuitive, and another thing that comes to mind is that it can feel overwhelming when workflows become large and complex. Troubleshooting can take extra time when there are multiple dependencies, jobs, and integrations running together. Better visualization of workflow relationships and easier debugging would really help. I would also appreciate seeing more simplified onboarding and documentation for newer users, as there is a learning curve at the beginning. Another improvement area could be smarter analytics or AI-driven recommendations, such as proactively identifying workflow bottlenecks, failed job patterns, or optimization suggestions instead of relying mostly on manual monitoring. From an operational perspective, faster configuration for integrations and cloud-based workflows would make implementation smoother, especially in environments working heavily with APIs and data pipelines.

I have covered the main points regarding needed improvements. Overall, the platform is very capable and reliable for automation and workflow scheduling, especially in data-heavy environments. Most of the improvements I want are around making it easier for day-to-day use, such as a more intuitive UI, simpler troubleshooting for complex workflows, better onboarding for newer users, and more intelligent monitoring or optimization insights. The core functionality is strong, and the biggest opportunity is improving the overall user experience and simplifying operational management.

I have three years of experience in my current field.

I find ActiveBatch by Redwood to be pretty reliable and stable for the kinds of workflows we run. Most of the scheduled jobs and automated processes run consistently without needing much manual intervention, which is important when dealing with recurring ETL pipelines, reporting workflows, and integrations across systems. From my experience, uptime and execution reliability are really strong. Once workflows are properly configured, they can run continuously and predictably, reducing operational delays and manual follow-up work. There are occasional issues during more complex workflows or dependency-heavy jobs, but nothing unusual for large automation environments. Most of the time, the monitoring and alerting features help identify issues early on before they become major ones, so overall, stability and reliability are definitely among the stronger aspects of the platform.

From my experience, the scalability of ActiveBatch by Redwood is one of its stronger areas. It handles large workflows and increased workloads well, especially in environments with recurring automation tasks and multiple integrations running together. As workflows grow, the platform is still able to manage scheduling dependencies and monitoring reliability without needing much manual intervention. For example, in data-heavy processes involving API integrations, reporting, and ETL workflows, it supports growing workloads while also maintaining stable and organized execution. That is one reason it works well in enterprise environments; it can scale from smaller scheduled jobs to much more complex operational workflows over time.

I did have some interaction with the customer support team for ActiveBatch by Redwood, and overall, I would say my experience was positive. The support and documentation were helpful when dealing with workflow setup, troubleshooting, and integrations. Most common issues could be resolved fairly quickly through documentation or guidance from the support side. What stood out to me is that the platform has a lot of features, so having responsive support really helps when workflows become more complex. Reviews from other users frequently mention strong customer service and responsiveness as one of the better parts of the platform. For very specific or advanced workflow scenarios, troubleshooting issues could still take time, especially when multiple systems or dependencies are involved, but overall, I would describe the support experience as reliable and useful during both the learning and operational use.

Before using ActiveBatch by Redwood, a lot of workflows were handled through a mix of simpler scheduling methods and more manual coordination. Some jobs were managed through basic task schedulers, scripts, or separate scheduling tools, but those approaches became harder to manage as the workflows grew and became more complex, involving multiple dependencies, APIs, and reporting processes. The main reason for moving towards a platform like ActiveBatch by Redwood is really around centralization and automation, making it easier to manage workflows in one place, monitor jobs more effectively, and reduce manual intervention. The biggest improvement was having better visibility into the workflows and more reliable handling of dependencies across different systems and environments.

Before choosing ActiveBatch by Redwood, I remember that other automation and scheduling options were considered, but mostly simpler schedulers and workflow management tools. ActiveBatch by Redwood stood out because it provided a more centralized approach for handling complex workflows, dependencies, integrations, and monitoring in one platform. Compared to lighter scheduling tools, it felt more scalable and better suited for environments requiring ETL processes, API integrations, and cross-system automation. The decision was less about replacing a single exact tool and more about moving towards a platform that could better support growing operational and automation needs over time.

I was not directly involved in the pricing, setup cost, and licensing decisions for ActiveBatch by Redwood, so my experience is from the user and workflow side rather than procurement. However, based on how the platform is used, it felt more like an enterprise-level solution designed for larger automation environments. The setup and implementation definitely seem to require some planning and configuration upfront, especially for complex workflows and integrations. In terms of value, the main benefit comes from the amount of manual effort and operational time saved through automation. Although the platform may require a bigger initial investment compared to simpler scheduling tools, it can provide strong long-term value in environments with large-scale workflows and recurring operational tasks.

I have seen a noticeable return on investment with ActiveBatch by Redwood, mainly through time savings and improvement in operational efficiency. Before automation, a lot of recurring workflows such as data processing, report scheduling, and monitoring jobs required more manual effort and follow-ups. Automation with ActiveBatch by Redwood significantly reduced the repetitive operational work, improving analyst productivity by around 25 to 30%, mainly because less time was spent manually triggering these jobs, checking dependencies, or fixing missed schedules. It also helped reduce operational delays and errors, indirectly saving time for the team and improving consistency. I would not frame it as reducing employees but more as allowing teams to focus on higher-value analytics and operational work instead of repetitive manual tasks.

I was not directly involved in the pricing, setup cost, and licensing decisions for ActiveBatch by Redwood, so my experience is from the user and workflow side rather than procurement. However, based on how the platform is used, it felt more like an enterprise-level solution designed for larger automation environments. The setup and implementation definitely seem to require some planning and configuration upfront, especially for complex workflows and integrations. In terms of value, the main benefit comes from the amount of manual effort and operational time saved through automation.

Before choosing ActiveBatch by Redwood, I remember that other automation and scheduling options were considered, but mostly simpler schedulers and workflow management tools. ActiveBatch by Redwood stood out because it provided a more centralized approach for handling complex workflows, dependencies, integrations, and monitoring in one platform. Compared to lighter scheduling tools, it felt more scalable and better suited for environments requiring ETL processes, API integrations, and cross-system automation.

ActiveBatch by Redwood has positively impacted my organization, and I would say my advice would be to start with smaller workflows first and gradually expand to automation later. Although this is a strong platform for workflow automation and scheduling, I would not give it a full point because of the complexity. I think the UI could also be more modern and intuitive in some areas, especially for new users trying to understand the workflows quickly.

The learning curve for new users with ActiveBatch by Redwood is moderate at first. It is not extremely difficult, but because the platform has a lot of features and workflow options, it takes some time to fully understand how everything connects together. For simple scheduling tasks, getting started is fairly straightforward, but when workflows become more complex with dependencies, integrations, and multiple jobs, it definitely requires more hands-on experience. Once I got familiar with the interface and workflow structure, it became much easier to use, so overall, I would say it is powerful, but new users may need some time and practice in the beginning.

The documentation and support resources available for ActiveBatch by Redwood are generally helpful, especially for understanding the basics and setting up workflows. The documentation covers most common tasks clearly, which is useful when learning scheduling integrations and workflow setup. I also found that examples and guides helped a lot in the beginning. That said, there are times when it takes extra digging to find the exact information needed for more complex workflows or troubleshooting. Since the platform has many features, newer users may still need hands-on practice to fully get comfortable with it. Overall, the support resources are solid and definitely helpful during the learning process.

My biggest advice for those looking into using ActiveBatch by Redwood is to first understand your workflow needs before implementation. The platform works best in environments with many recurring operational tasks, ETL processes, reporting workflows, or integrations across multiple systems. If a team is still handling many processes manually, that is where they will probably see the most value. I also recommend starting small instead of trying to automate everything at once. Begin with a few important workflows, get comfortable with scheduling and monitoring, and then gradually expand from there. I suggest investing time upfront in workflow design and documentation, as having a clear structure makes troubleshooting and scaling much easier later. I would say do not treat it as just a simple scheduler; it is much more useful when used as a centralized automation platform that connects different systems and workflows together.

I would say overall that ActiveBatch by Redwood is a strong and reliable platform for workflow automation, especially in environments with complex operational processes. The biggest value comes from how much manual effort it can reduce once workflows are properly set up. It helps bring better consistency, visibility, and reliability across the processes. I also think it is a platform that becomes more valuable over time; the more workflows and integrations centralized into it, the more efficient it becomes. Organizations should be prepared for a bit of a learning curve in the beginning, especially when dealing with large or dependency-heavy workflows. However, once teams get comfortable with it, it can become a really important part of operational automation and workflow management. I would rate this platform an 8 overall.

My main use case for ActiveBatch by Redwood is that I handle the ActiveBatch by Redwood maintenance through upgrades and provide access and complete support to the end users. I manage all the ActiveBatch by Redwood handling, including errors or exceptions that come through the ActiveBatch by Redwood application and daily monthly maintenance as well.

A quick specific example of a task I manage with ActiveBatch by Redwood is my day-to-day activity, which starts with the plenty of jobs that are running. The main view for me is the Operations view, where I monitor all jobs related to it. If any jobs that have been monitored are running or in the process of preprocessing and have been stuck for a long time, then it alerts us. If ActiveBatch by Redwood hangs up, we have a secondary node as well. We failover to that node so that we can act on the primary node and minimize outages for our end users or customers, ensuring nothing is stopped.

The best features ActiveBatch by Redwood offers include its robustness and user-friendliness. What I appreciate the most about ActiveBatch by Redwood is the interactive session, as they have introduced an AI tool. Previously, we used the ASCII portal to ask questions, but now I can easily manage it using the AI tool, where I input logs and receive answers.

The addition of AI has made troubleshooting and supporting users through ActiveBatch by Redwood quicker for me. The ASCII portal sometimes provides incorrect input for queries, but when I type them into the AI, I receive relevant feedback and information. I share the troubleshooting steps with end users, removing sensitive information such as IP addresses from the logs.

ActiveBatch by Redwood has positively impacted my organization by efficiently managing a significant volume of data and workflow between our database and applications on the web browser. It has been a great experience, as we manage almost 5,000 clients without any hiccups.

The current feedback I receive from my end users regarding ActiveBatch by Redwood highlights issues with the tabs or panes during job modification. When the next user monitors it, they need to close the pane or job and reopen it to see the changes reflected. If the end user makes an update, it will not be visible unless they start from the beginning again. Implementing a refresh button would be helpful for real-time updates when the end user needs to see changes immediately.

We currently face issues with the web console of ActiveBatch by Redwood. When users operate through an RDP session, every user has their own ActiveBatch by Redwood application. However, on the web console, users encounter daily activity issues where the job instances do not appear or update correctly, and they cannot view the latest logs. This issue is only present on the web console, as the application itself works without any problems.

ActiveBatch by Redwood can be improved by adding more features, as we are not currently handling cloud-based applications like S3 buckets and Azure. Connecting to these cloud platforms would be a helpful enhancement.

I have been using ActiveBatch by Redwood for eight years.

ActiveBatch by Redwood is stable.

ActiveBatch by Redwood's scalability is excellent; it experiences minimal failures and outages. The company I work for operates as a 24/7 service without any scalability issues, as it remains up all the time.

Customer support for ActiveBatch by Redwood is fantastic at the level one tier. The first response in the AI ticketing system is prompt, but we often need to escalate issues to level two or three for solutions related to long-standing problems.

Positive

I did not previously use a different solution before ActiveBatch by Redwood.

I have seen a return on investment with ActiveBatch by Redwood, as it is cost-efficient and has improved time management. We require fewer team members to handle operations due to its robust automation.

My experience with pricing, setup cost, and licensing for ActiveBatch by Redwood has been great; we recently renewed our license, and it was a smooth process without any issues.

We did not evaluate any other options before choosing ActiveBatch by Redwood; we have used it from the very beginning.

I have noticed metrics and improvements since using ActiveBatch by Redwood, such as alerting active operations. For example, if a queue handling around 500 jobs gets stuck in pre-processing mode, we receive alerts about it. We investigate particular queues, and if the issue lies with ActiveBatch by Redwood, we switch to a secondary node in the availability zone to minimize job outages, reboot the primary after ensuring it's healthy, and run tasks on the secondary node if necessary.

My advice for others looking into using ActiveBatch by Redwood is that if a ticket is categorized as medium priority, it should be handled promptly, as labeling it as high priority doesn't add value to the ticket itself.

My company does not have a business relationship with ActiveBatch by Redwood beyond being just a customer.

On a scale of one to ten, I rate ActiveBatch by Redwood a nine.

My main use case for ActiveBatch by Redwood is automating complex job scheduling and workflow orchestration across multiple systems.

I also automate end-to-end IT maintenance tasks such as system health checks and report generation.

ActiveBatch by Redwood has positively impacted my organization by improving efficiency through reducing manual intervention and minimizing downtime, which made operations significantly smoother.

We saw around a 30 to 35% reduction in manual task time and a notable drop in errors with ActiveBatch by Redwood, thanks to the automation capabilities of this tool.

The best features ActiveBatch by Redwood offers for me are its cross-platform integration and the ability to create complex workflows visually.

Cross-platform integration helps my daily work as we automate tasks across Windows, Linux, and other cloud tools seamlessly. The visual workflow allows us to design processes quickly and clearly.

One way ActiveBatch by Redwood can be improved is through a more intuitive user interface for new users.

I rate ActiveBatch by Redwood an eight out of ten because it is powerful, but a perfect score would require a more modern, user-friendly interface and slightly faster performance.

I have been using ActiveBatch by Redwood for about three years.

ActiveBatch by Redwood is highly reliable and runs jobs on schedule, while the notification system keeps us updated on any failures or successes.

ActiveBatch by Redwood is stable and performs much better than my previous solutions.

The scalability of ActiveBatch by Redwood is excellent; we expanded from smaller jobs to larger, complex workflows without any issues.

Customer support for ActiveBatch by Redwood has been responsive and knowledgeable whenever we need any help.

I would rate the customer support of ActiveBatch by Redwood a solid nine out of ten; it has been very reliable and helpful.

We previously used a simpler in-house scheduling tool, but we switched to ActiveBatch by Redwood for its broader automation capabilities and scalability.

Pricing for ActiveBatch by Redwood is fair for the features offered. Setup took some time but was manageable, and licensing is straightforward.

I saw a roughly 25% time saving on routine operations with ActiveBatch by Redwood, and we needed fewer manual interventions, allowing my team to focus on other priorities because of this tool.

Before choosing ActiveBatch by Redwood, we evaluated alternatives such as Control-M and Jenkins, but ActiveBatch offered better integration for our needs.

While support for ActiveBatch by Redwood is good, I think even more detailed documentation or tutorial content would help new users ramp up faster.

I would advise others looking into ActiveBatch by Redwood to start with a clear understanding of their workflows and take full advantage of the trial period to tailor it to their daily needs. I gave this product a review rating of eight out of ten.

My main use case for ActiveBatch by Redwood is file processing. I use ActiveBatch by Redwood for file processing for debit card transactions.

The best feature that ActiveBatch by Redwood offers is the user interface. I find the user interface particularly helpful because it is easy to set up new jobs and recurring jobs. The ease of setting up jobs is the main highlight for me.

ActiveBatch by Redwood has positively impacted our organization because we are able to process files very effectively. For my team, effectively means we can easily set up a new job in about a day or less.

I believe ActiveBatch by Redwood could be improved because the UI could be modernized.

I have been using ActiveBatch by Redwood for three years.

In my experience, ActiveBatch by Redwood is fairly stable.

ActiveBatch by Redwood performs adequately in terms of scalability and handling growth or changing requirements.

My advice to others looking into using ActiveBatch by Redwood is that it is a pretty good no-code solution. I would rate this product a 6 out of 10.

ActiveBatch automation is one of the best automation tools for managing the workload of an organization. 

The best part is that It's directly connected to the heart of our system where we run more than 10,000 jobs on a daily basis. It helps us to save a lot of time by doing all the repetitive tasks very efficiently with no errors. 

It serves as a centralized hub for overseeing, scheduling and governing workflows, tasks, and jobs, encompassing functions such as task scheduling, data manipulation, and file transfers, among other capabilities.

ActiveBatch proves to be a flexible and easy-to-use solution for automating workflows. The inclusion of a drag-and-drop interface and impressive integration features significantly simplify the process of creating workflows. 

The predefined steps for task automation greatly enhance convenience. The capability to effortlessly establish connections with servers, applications, and services offers the opportunity to seamlessly collaborate with other software concurrently. 

Any large business or organization that wants to manage its workload effectively and with the least amount of room for error might choose the ActiveBatch Automation tool.

The mechanism of alerting is at its peak performance, offering notifications for any job that experiences a failure, encounters extended processing time or successfully reaches completion. 

By implementing a sophisticated scheduling mechanism, the system allows for the precise triggering of jobs at user-selected frequencies, enabling a seamless and automated execution of tasks according to specified time intervals.

The incorporation of plug-and-play API features into the software framework empowers developers with a simplified and streamlined approach to integrating external functionalities seamlessly

Occasionally, I find myself contemplating if there is room for improvement in the user interface (UI), and envisioning that with certain enhancements. The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application.

New users might encounter a minor setback due to the absence of readily accessible training videos, which could have otherwise proven to be an invaluable resource in aiding their initial familiarization with the platform, potentially hindering their seamless onboarding process and delaying their ability to harness the software's full range of capabilities to its utmost potential.

I have been using ActiveBatch for eight months now.

ActiveBatch automation is one of the best automation tools for managing the workload of an organization.

We run more than 10,000 jobs on a daily basis and it is always handled effectively.

The interactions with technical support have been positive.

Positive

I have used the UC4 Automic tool, however, when I started using ActiveBatch, I noticed a notable improvement in the efficiency of managed file transfers, facilitating the timely movement of files, including those of a more intricate nature, with enhanced ease and effectiveness.

The initial setup and configuration are time-consuming. 

ActiveBatch supports intelligent automation and has a user-friendly interface.

It has helped many times in saving on the SLA.

ActiveBatch helps save time by doing all the repetitive tasks on a daily basis. During the patching activity, the schedulers can be stopped. It also helps by alerting us if any system/job is down so that SLA can be saved. Overall, ActiveBatch Automation stands as a dependable cornerstone for ensuring the seamless operation of our tasks.

We send out requests to leaders for the inputs, and the inputs are either shared via emails or uploaded on SharePoint. Then, we download that data process them, and convert them to consumable format in Excel, the excel files then get uploaded onto SQL servers which are connected to visualization tools, post refresh we publish the reports onto services.

The entire process of scheduling, running DB jobs, applying security, refreshing DB, publish was done manually and repeated whenever new inputs come in, now ActiveBatch has streamlined the entire flow with a minimal error rate.

My team consists of five associates. We mainly deal with pricing, sales operations, reporting, forecasting, and several other analytics.

The use of ActiveBatch has made all our lives easy by automating a lot of manual repetitive tasks that we do on a daily basis. We save hours and effort aand gain a high accuracy rate.

Approximately ~20 hours of manual effort have been reduced to ~5 hours with the help of ActiveBatch.

It has enabled us to work on multiple platforms at the same with its capability to integrate with other applications and web services.

The most valuable feature is the drag-and-drop functionality, which makes it a very easy-to-use software for anyone who is working on the software for the very first time. There is minimal coding knowledge required.

I like the ability to integrate with other applications, software, and cloud services which empowers anyone using the software to work on various platforms at any given time.

The job scheduling feature increases the efficiency of the software as it requires minimal manual intervention.

ActiveBatch is a powerful and robust workload automation tool that is the best in the market. I do not see major setbacks in the software. However, there are a few things that need to be improved to make it more efficient and provide a better user experience, such as: 

• reducing the lag
• having more security privileges
• pricing that is more affordable.

However, these minor improvement areas would not impact the efficiency or accuracy of the software. ActiveBatch still remains on top of all the workload automation software out in the market.

I've used the solution for one year.

I do not foresee any challenges with the software scalability, bigger organizations can easily deploy however pricing might be the primary concern for smaller organizations.

I do not have a case to bring out as I have not faced an issue and have never needed to reach out to support.

Positive

There was no transition from similar software.

The initial setup is a little complex; providing a well-documented user guide would resolve the issue.

We handled the setup in-house.

In terms of ROI, the solution has saved manual hours (from ~20 hours to ~5 hours in a month) and increased accuracy by ~17%.

The initial setup is a little complex. Subscriptions can be made for a group at a reasonable price.

I did also evaluate Jira.

The software is definitely the best. With minor fixes, it could be great and remain very competitive.

As sales operations analysts, our main task is to deal with cumbersome data, forecasting, and sharing these cleaned data with our global partners.

We clean these data and store it in consumable Excel files and then upload these to SQL servers which are in turn connected to visualization tools and we often refresh these tools to publish our dashboards in service.

ActiveBatch has streamlined all these steps with automation and no manual intervention which has helped to decrease errors.

ActiveBatch Workload Automation is a super robust application FOR Regular SQL tasks or other file maintenance which in turn can help us to free up the time that we spend on working on repetitive tasks. Approximately ~25 hours of manual effort has been reduced to ~5 hours.

It also offers a centralized platform for managing activities across many environments, applications, etc.

ActiveBatch has made our lives very easy by automating a lot of features which has led to fewer errors and more accuracy.

The product:

1. Is very easy to use, has a good user interface, and not many prerequisites are needed.
   
2. Offers a centralized platform for managing activities across many environments, applications, etc.
3. Offers good automation where manual intervention is significantly reduced - which has led to fewer manual errors.
4. Does frequent job runs and the load on the server has reduced.

There are a few improvements needed:

1. ActiveBatch Workload Automation is a super robust application for regular SQL tasks or other file maintenance - although it needs a few tweaks.
   
2. ActiveBatch's user interface needs an update as some features are hidden and repetitive clicks are needed to access those.
3. ActiveBatch scalability can be increased to help working on larger workloads.
4. ActiveBatch event-based triggers are not reliable at times.
5. ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides.

I've used the solution for one year.

The stability is good.

I'd rate the scalability nine out of ten.

Customer support response was a bit slow when we needed a technical escalation.

Positive

The initial setup was a bit tedious due to a lack of proper user guides.

We implemented the solution via our in-house team.

ActiveBatch has saved a significant amount of manual time (from ~25 hours down to ~5 hours), hence bang for the buck.

Setting up the solution was quite hard initially. The pricing is pretty agreeable for all our requirements. The licensing is easy as we had the choice according to our requirements.

I did not evaluate other options as Active Batch was the top choice and we opted for this without any second thoughts.

ActiveBatch is a robust automation software and it is our go-to option.

ActiveBatch helped us to streamline our IT workflows and improve overall efficiency. It is the most essential tool in our Infrastructure now. 

The best part of ActiceBatch is its user-friendly Interface, which feels easy to use even for a user with limited technical experience. 

We can configure and design complex workflows. 

It also offers pre-built templates and wizards which can be used to easily and quickly create automated workflows. 

ActiveBatch also includes the option to implement it in on-premises, cloud, and hybrid deployments.

Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis. We can set tasks for daily, monthly, or weekly runs. 

This powerful and reliable tool can be implemented in small businesses and large enterprises that are looking to automate their IT workloads. 

It is used to trigger tasks at specified frequencies, We have also integrated ActiveBatch with different services and applications.

There any many outstanding features in ActiveBatch. For example, error-handling functionality has decreased the errors and issues triggered, which has improved the accuracy of the results. 

ActiveBatch is a valuable tool in our organization as it has increased efficiency and time consumption. It handles large workloads, and batch jobs and automates transfers effortlessly. 

The alerting feature helps notify and address the status of the jobs running and keeps the operations uninterrupted.

After upgrades we are facing a few issues and errors triggered, so focusing on this would be appreciated. Some of the advanced features in the user interface are a bit confusing even after referring to the documents. 

Improvement in support is much needed; there is a lack of training videos that would help us gain more understanding of the product. 

Sometimes, triggering fails and we have to face a lot of issues, Initially while setting up installation we will be confused. 

Integration with other applications should be improved

I've been using ActiveBatch Workload Automation for approximately two years.

Initially, we were facing a lot of difficulties in monitoring the scheduled jobs. We had to create multiple tasks for managing servers and get it done by using change requests. It was very hectic and time-consuming as we had to monitor each and every server manually. 

After implementing ActiveBatch workload automation we were able to automate all our tasks and build reliable workflows. It provides an option of triggers to eliminate errors and automate triggers based on events/actions. Monitoring, scheduling, and controlling workflows of the jobs and tasks have been simplified in half the time.

We have to monitor our backup servers on a daily basis, creating dump files and verifying all the active master servers that have gotten at least one dump parsing data entry. It's helped with checking servers with error status and analyze/fix/report and monitoring for the latest dump files in the server. These were the most time-consuming tasks and required more attention. Active Batch has helped us to automate these tasks by reducing resource usage and giving us more time for extra productive hours other than monitoring. We are able to track down the server failures easily and fix the issue within the SLA targets thereby achieving effective and improved business processes.

ActiveBatch is highly reliable and scalable for all our automation work. The tool provides excellent service management and intelligent automation for scheduling complex jobs. 

It processes heavy workloads on servers hassle-free - proving the tool's stability. 

ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy. With the help of ActiveBatch, we were able to reduce a lot of scripting work for automation tasks as the tool supports max scripting.

Overall, ActiveBatch is highly recommended if you are really struggling with daily monitoring tasks.

I don't see any drawbacks with the usability, however, the documentation part can be improved with some additional guidance about the features and their usage. I have faced struggles to understand, set up the tool, and implement it in my early days as a new user. 

The UI also could be a little more advanced in the next release along with some video tutorials - such as providing a user guide. 

I am using ActiveBatch for two years.

Customer support is good. We were able to get in touch with them when we had queries.

Positive

We did not use any software before; it was completely manual.

As a beginner, the setup was pretty hard due to a lack of deep guidance or documentation.

After automating, we are able to achieve our SLA targets thereby reducing the SLA breach and increasing the KPI by 98% - which is a great ROI.

Setting up the environment was quite hard initially. The pricing seemed to be pretty decent in the market for all our requirements. The licensing is easy as it can be chosen according to the plan that makes the most sense.

We evaluated other software, however, ActiveBatch seemed to be a perfect fit for our requirements.

Active Batch is my go-to option for all my automation-related work.

We have a security project where we need to perform daily scans on a number of our servers and network infrastructure components and keep a check on their health and status. We have implemented the ActiveBatch to perform endpoint security scans on our environment for each and every component and provide us with a detailed report stating their health as well as updating on that server and components that need upgrades. We have scheduled the scans to take place every 12 hours on a daily basis and provide the major stakeholder with detailed reports. 

ActiveBatch has really improved our project by automating the endpoint security scans on our servers and also other components of our environment. 

Being a security project we should have a complete picture of the health of each and every component as well as the servers that need to be upgraded to avoid any malware attacks on non-upgraded servers due to existing vulnerabilities. This has saved associates a number of critical business hours that can be used to concentrate on critical business tasks rather than spending them performing repetitive security scans.

The automation feature is a very valuable feature as the associates do not have to worry about performing repetitive tasks (i.e. endpoint security scans on a daily basis) that would take several hours to complete on a daily basis.

It is also faster and more efficient in conducting endpoint security scans compared to associates who perform it manually, reducing the scope of error and also providing a detailed report on each and every component present in our environment. The reports are very detailed and visually appealing that is shared with major stakeholders.

This product is the gold standard of all the automation tools around. You can schedule jobs easily. It is faster and also more efficient. The product also provides a detailed dashboard after the endpoint security scans are performed. 

The only service that needs improvement is integration support. There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment. The team could create more documents and also publish blogs to support customers with queries. 

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