VisualCron Reviews

We're using VisualCron to manage jobs, schedule tasks, and even send emails that notify you whenever a job or task fails. It's a task management tool.

As we're monitoring everything through VisualCron, the tool makes the whole process easy. The Windows Task Scheduler previously handled new tasks, and it was more complicated because you had to make some changes, stop, then redeploy Windows Task Scheduler. In VisualCron, it's much easier because you just have to go into a specific job, add a new task, then set up the sequence. If a task fails, you'll get an email notification from VisualCron, and then you can rectify the issue.

Using the Windows Task Scheduler means you have to do some coding while using VisualCron means the tool takes care of the coding from the backend. You're just using the visual interface of VisualCron, creating the logic, and telling the tool what actions need to be performed, so VisualCron would take care of everything on the backend for you, which helps you manage time better.

What I found most beneficial from VisualCron is that you can directly connect it with different databases, user accounts, and credentials. You can run queries from one machine to another using the credentials, unlike  PowerShell, that's run by the machine itself. With VisualCron, you can directly ask other machines and run requests through user credentials.

Suppose you have an AWS or Azure environment. In that case, you can maintain the connection between on-premises and cloud-based machines, which is the type of setup in the organization I'm working for. You can directly call some of the services via VisualCron on your local on-premises machine, and I found that an excellent feature of the tool.

I want to improve the UI in VisualCron, as it's not as user-friendly, particularly when setting up the task scheduler. If you're familiar with the tool, then no problem, but if not, you'll have a problem typing text because sometimes, the cursor points to other places, so there's an issue with text box alignment in VisualCron. That was painful for me when I was just a VisualCron novice, but when you become used to it, there won't be a problem.

An additional feature I'd like VisualCron to have in its next release is CI/CD support, though my organization uses GitHub for it. It'll be a plus point for VisualCron if it can support CI/CD and have GitHub features for DevOps that it currently doesn't have.

I've been using VisualCron for almost two years. I'm still using it.

VisualCron is a pretty stable product so far.

Scalability-wise, I'm not one hundred percent sure, but you can install VisualCron on different machines. You also have the option to handle it from one system, but it becomes more risky for an organization if you have everything on one system.

Technical support for VisualCron is excellent, as the team quickly responds via email. If there's an urgent issue and you're a paid user, the team will directly call you based on the region you're in, try to understand your scenario or problem, then guide you on how to solve it.

On a scale of one to five, my rating for VisualCron support is a four, as I'm pretty satisfied with the support overall. However, some users may not be satisfied, probably because of not following instructions from the technical support team.

Setting up any new product for the first time could be a bit troublesome, but what's good about VisualCron is that it has an online community where you can ask questions and get fast replies. There's a community that can help you out, even with how to set up VisualCron. You can search for information or ask a question to the community to get help on your exact scenario and how you can achieve your goal.

The initial setup for VisualCron had a minimal requirement. Hence, setting the tool up was pretty straightforward for my team, but in terms of using the task scheduler, my team didn't know how, but there's a big community where my team got the support it needed.

On a scale of one to five, I'm rating the initial setup for VisualCron as three. It wasn't difficult to set up, though it had some challenges.

The organization is paying for the VisualCron license, so I'm not aware of the current pricing for the tool.

VisualCron is the first RPA tool I've used. I haven't evaluated others, though my organization previously used the Windows Task Scheduler for scheduling tasks.

I'm pretty satisfied with VisualCron, so my rating is eight out of ten, though I'm not using all its features. It's been a beneficial tool for me. In specific scenarios, a new user could face a bit of difficulty using VisualCron. Still, once you get used to it, it's like driving a car on the highway where you could face some issues but eventually solve the problems as you travel.

Around fifty people use VisualCron within the organization. It's used twice a week, and the DevOps team uses it more often, depending on the projects.

We use it for replacing files from our FTP server to our network work folders or as an email selector for invoices. We receive invoices into a certain mailbox depending on the sender address where we make mail triggers. In the trigger, we can manage what to do with the attachments:

1. We put the invoice into a process folder. 
2. We put the attachments into a subfolder where we merge the invoice with attachments. 
3. Once you make the job/trigger in every mail, it is processed automatically.

VisualCron is a very powerful program to automate different steps in your business processes. We use it to automate replacing files and inform departments about the replacement.

Mail trigger: When a mail is delivered into a specific inbox, you can fire off your task depending on this.

Event trigger: When a file is placed in a certain folder, you fire off your task depending on this.

There are a lot of tasks that you can use for all kinds of stuff. 

It's very useful to use variables which help you to specify some jobs.

The forum is very useful.

There are some conditions in the mail trigger, but you can only use them as an "AND" condition, not as an "OR" condition. This is an improvement that could be useful. For example, some people put "invoice" in the subject and others put "invoice" in the body. If I want to make a trigger for everybody whose sending invoices, I have to make two jobs for this now.

Seven years.

Good.

Very good.

Michael and Henrik from support are very kind, helpful, and almost always available for questions when there is something wrong with a job (you have made), but is not working anymore. The have helped me often with different things. 

The forum is very useful for solutions on things you want to change or problems you are struggling with.

No.

Straightforward with the help of support.

In-house.

One month.

No.

We set up nightly sync tasks in which it is making different requests.

Helped us reduce manual steps.

Nightly sync tasks.

The error timeout and info could be better. When making web request calls, it will time out sometimes and we won't get any useful info out of the error response.

Since 2017.

Nine out of 10.

Eight out of 10

Support is AAA+, fast, and very detailed. 

Yes, but VisualCron was chosen by our client. 

Straightforward.

In-house.

ROI is 95 percent.

I am not be aware of what our clients evaluated as other tools.