Hi
It could be just me, but I find it a bit confusing with the name of the option 'activate selected triggers'.

Since there is a column 'Activated' my first though was that if I click that it will just mark all of the botflows as activated, but instead it is for starting it. Maybe the 'Activate' word could be changed to 'Start' or 'Run'?

Also, it would be nice to be able to run the flow manually directly from the 'Botflow' window and not only from scheduled windows.

Would it be possible to do one of below, or even both.

1. after an execution has failed then give an option to try to run again. And if the run was successful, then the status would change from "failed" to "success with manual help" or something

2. Having the option to add a note to histories of executions. When a Botflow is failing I would normally go and start the script manually, but the history in Orchestrator has no record of this, and it will look like the script did never run. This way we could state in the history "I ran this script manually on 1/4 20 at 10. a.m., the error occured due to...... "

Thank you in advance and keep up the good work with this tool
Ghita

Hi,
Not sure if this is possible at all, but if so, it would be nice that the task that runs the python script will run as "minimized" automatically. I mean instead of the window popping up once logon or fresh start.
If possible even as "hidden"
Thanks
Ghita

Currently, if the SMTP server does not require login, the SMTP functionality fails

All cmd prompt inputs are case sensitive

Would it be possible to get a pop-up with a timer before timeout will cause the script to close down.
In some cases we have scripts being paused for a certain amount of minutes where we have a chance to decide whether or not we will do some corrections to the script. If we decide to do a correction. the scripting time may cause the script to time-out and there is no chance to stop this.
If a pop-up would show saying (Botflow will time-out in 60, 59, 58..... to discard press "discard") and if we press discard then Orchestrator should ignore the time-out this one time, if no-one will press discard then after the 60 seconds Orchestrator should just time-out as always.

After the ending of DST this year (in Denmark), the scheduled triggers in the orchestrator are scheduled 1 hour ahead of time. I'm not sure if DST compatibility is intended, but if it is, it's buggy :)

If you change the path of a botflow, it will no longer show in the statisitcs in the Dashboard. Wouldn't it be possible to do the statistics from the "NAME" instad of the "PATH".
I have already had a couple of clients that have renamed botflows, or added extra folders and by that changed the PATH of a botflow.
Thanks
Ghita

Hi
I just encountered orchestrator skipping one scheduled robot. After looking at the console I noticed, that it did a restart at 10:01:02 and the robot was supposed to run at 10:01:00. However in this case i guess the 10:01:00 happened while the orchestrator was restarting.

I think it would be useful to have a check that there are no robots scheduled in the next 5 mins or so before doing the restart.

Console:

Schedule:

Executions:

When I register a botflow there is an option "Queue if already running". I use the same bot at the same time, on several machines, but if I uncheck this option when registering the botflow, it limits me to one execution of the bot even if I have 10 machines available to run at the same time. Would it be possible to include something similar in the schedule? That way it would only create a queue on free machines and not on machines that already have a queue thinking about multiple machines at the same time, with the same bot.

Or in the botflow registration itself, but another option analyzing the available machines and not limiting it to a single machine.

When a botflow times out, Orchestrator is not able to run another botflow without me opening and closing FoxBot manually.

It looks like Orchestrator closes FoxBot on a timeout, but doesn't tell the schedule to check if the next bot can be opened.

If possible at all, it would be cool if Orchestrator could run as a service instead of in terminal.

While testing out the new 0.3.8 build, I've noticed that the version is incorrectly displaying 0.3.7.

An extension of #14, it should be possible to specify that a bot is only available during a certain time frame, similar to how the triggers work.

Would be great if it was possible to assign apps to each bot (or enable apps on each bot). Same should probably be done with botflows to bots unless a validation could be made via filename extention.

Purpose is to avoid attempting to run one type of automation (eg. Uipath) on a bot that only runs Nintex RPA.

Hi,

If I have a trigger with two bots, and both bots are available, the trigger works perfectly fine, it will start the botflow on 1 of the available bots.
If I have one of the bots being occupied, the botflow will start on the available bot, but once the occupied bot gets available, the same botflow will also start on this bot now.

Is this a bug, or am I doing something wrong?

Thanks
Ghita

Hi, so I know that it is possible inside your botflow to make lists, and actions that will check if today’s date is a national Holiday and if so, close the Bot, and so on, bu I was thinking if it would maybe be possible already from the Orchestrator. Was thinking something like:
When choosing whether or not the Botflow should run on weekdays and weekend days, maybe there could be a number of checkboxes for National Holidays... run on National Holidays: “DK, SE, DE, US...” all should be checked from start, but you could then un-check the one you need your Botflow NOT to run on. I know that there should be contact with calendars of each country, and I do not know if there is any “smart” way to script that, but if so, this would be very cool.
Thanks
Ghita

To enhance user experience an open file dialog should be added, so it's possible to pick a file rather than only being able to type/paste the file path.

Example filepath for:

• Apps
• Botflows

Hi,
Is there any reason that the notification email about a script being queued will come no matter if a script is "actually" queued or not?
If nothing is running on the BOT, I will receive a notificatoin that the triggered Botflow is queued, and seconds later I will receive a notification email that they Botflow is started.
I believe it would be more usefull if the email notification saying that the Botflow is queued will only come when the botflow is acutally queued due to another botflow being in process.
Thanks
Ghita

Hi,
Would it be possible to change the notification email subjects from:
[##] Botflow started: "FULL_PATH_BOTFLOW.RPA"
to
[## Botflow started: "BOTFLOW_NAME_ONLY"

I think the emails would be much more usefull this way. the full path can of course be mentioned in the body of the email still.

Thanks
Ghita

Would be great if the sending of notifications to the SMTP account by default could be activated or deactivated.
I would prefer having one email as sender and per botflow we can choose the receipient (which is already possible), but I do not want every single notification sent to the sending mail by default.
Thanks
Ghita

Hi,
It would be nice if it could be possible to choose "Copy trigger" in the dropdow in trigger views. We often have scripts that should run ever Monday and Thursday i.e. or every day at 10, 13, and 17 o'clock.

Thank you in advance
Ghita

I am missing some kind of overview of the total number of triggers per Botflow.
Once you have 10+ scripts it can be hard to keep track of the different triggers per Botflow.
If one Botflow is both triggered on a schedule, IMAP and API, it would be nice to be able to click the Botflow, and then have an overview of all the triggers both active and inactive for this particular botflow only.
I hope this could be an enhancement in the future.
Thanks and keep up the good work.
Ghita

Hi,

Mathias was helping me installing the orchestrator on a server that required bypassing the proxy, and he made a note for "next time" saying:

_**To be able to run the pip install commands on this machine, the proxy gateway must be defined in the CMD.

To do this, run this command:
set http_proxy=http://username:[email protected]:8080

Then perform the pip install commands "manually"**_

I want to update the Orchestrator to the lastest version now, and I ran the command, and I "think" I manually performed the pip install, but I am not sure if I did it correctly... propably didn't... :o/
Anyways, after the Orchestrator was installed, I can login to the Orchestrator (I get the login page), but after that I get:

@mbalslow maybe you know and can explain to me what I am doing wrong. :( When I do the set http_proxy command, "nothing happens", but it doesn't say error either, so I expect it to be okay...

Thank you in advance
Ghita

I have a couple of times lately thought that it would be nice if the Orchestrator version would be mentioned when you are actually in the website.
Instead of having to go to windows files to check which version is running on the particular machine, it could be mentioned in the top ribbon, or in a buttom corner in the website. Just somewhere.
Maybe I am missing it, and it is already there, if so, maybe you can tell me where to see it.
Thanks
Ghita

It should be possible to schedule job to be running from a date 1 until date 2, or possibly a set number of times.

Example:

• Run job every X (eg.12 hours) from the 20th and until the 28th each month
• Run job every X (eg. 12 hours) for Y number of times

Sometimes when executing a scheduled scripts from a mapped network drive, the Orchestrator says that it can't find the botflow.
But if i use the UNC path for the drive there is no problems.

Fx.

Not working: T:\Robotics Monitor v5.9.3 Scott Evil.rpa
Working: \basicofil01\bco\Robotics Monitor v5.9.3 Scott Evil.rpa

The error only occurs on some machines/drives. I have a suspicion that it could have something with the user rights to do.

I have several botflows that run on more than one machine at the same time, due to the volume of processes. When I create a schedule and select several machines, it directs to a single machine at a time for each execution of the schedule. No problem with that. But, what is the possibility of having an option in the schedule to schedule on all available machines at the same time, and not individually?

In the top of the dashboard, you have "Botflows running", "Botflow queued" etc. Maybe you could add an extra one called "Botflow scheduled today" which could show the no. of Botflows that are scheduled for today.
Just throwing ideas out there, I hope it is okay.
Thanks

Currently, the settings.py file for Django contains the following allowed hosts:

Where the last line only retrieves the IP of the current machine. I'd argue that adding the line socket.gethostname() by itself would be beneficial, as more often than not you access the webpage in a local environment by its name rather than its ip.

Using the other value in the array returned by socket.gethostbyname_ex() returns the hostname with the domain attached, and as such might be less useful than simply socket.gethostname()

Hi

I tried to set up the orchestrator to trigger a python script instead of a Foxtrot file and got into issue with library import:

[17/Jun/2020 09:53:13] "GET /login/?next=/ HTTP/1.1" 200 2161
Traceback (most recent call last):
  File "C:\send_email.py", line 1, in <module>
    import win32com.client as win32
  File "C:\Python\Python37-32\lib\site-packages\win32com\__init__.py", line 5, in <module>
    import win32api, sys, os
ImportError: DLL load failed: The specified procedure could not be found.
[17/Jun/2020 09:53:23] "GET / HTTP/1.1" 302 0

However when I run it on Orhestrator's python ("C:\AutomationOrchestrator\venv\Scripts\python.exe") file everyting runs fine.

Or if I trigger python script using python IDLE, it runs fine using the installed python (C:\Python\Python37-32)

Do you know why this could be the case?

Instead of linking a trigger to a single bot, it should be possible to link multiple bots to a trigger so that the activated execution will be assigned to the available bot of the linked ones.

IMAP trigger connection fails if IN/OUT folders have whitespace character in them.

Hi,
It would be cool to have another column under Botflow executions with the "time used" per botflow execution. So after Botflow starting time and Botflow ending time, another column mentioned the time interval between the two.
One more thing that would be awsome would then be a total in the buttom, like today there is a total botflow executions calculation in the buttom. Maybe even an average time spent on the selected botflows.
Just a thought, the tool is great, and I don't mean to be demanding, I only want the tool to be even better. :o)
Cheers
Ghita

Hi

would it be possible to add more details of why the botflow is pending?

This does not happen very often and don't know why, but sometimes the executions get stuck on one bot being pending. If this heppens it would be nice what orchestrator thinks is the reason for that bot to be pending.
in this case the flow was pending for around 40 mins before I cancelled it. Neither Foxtrot not foxbot was running on that account during that time and I opened and closed Foxbot before cancelling it to check if that would help, but it didn't. After cancelling it, I ran it through 'Schedule triggers' and it went to Running state right away.

Hi

After updating to 0.3.7 I have noticed that SMTP accounts page doesnt work anymore:

Add shortcut loads the 'Add SMTP account' page
Change shortcut results in similar error

Hi,

It would be great if you could change the status of an execution directly from the "Botflow Executions" page. For example via the drop-down menu. For whatever reason an execution might timeout, get interrupted, etc. and instead of deleting them i'd prefer to change the status so they don't stall the que. If multiple instances fail - for example if a server shuts down, it would be cool if you could mass select executions and update the status collectively.

Hi there!

This tool is amazing, thank you all for sharing it.

My issue is about: My Botflows always stay with status "Pending".

Let me explain my bot and setup:

Python script just to create a folder to test the BASICO (manually it works):

Create a new Bot:

Create a new App and test it:

Create a new BotFlow and test it:

Create trigger to test it running:

Dashboard displays status "Pending" 4ever:

Have anyone faced this problem like me?

Is there a way to solve it?

Have something that I'm doing wrong?

Thank you all.
Best regards

It would be nice to be able to scheduale lastday of month

After reinstalling Automation Orchestrator to newest version im having trouble logging in to the django site. I did a reset of the database, so now the database is empty except for the superuser "admin" that i created during installation.

When trying to login i get the error message "attempt to write a readonly database"

Both Install and setup_run_server has been run as administrator