It will begin on the interrupted task. However, it is best to test this as different version of AutoMate may behave differently. If you notice a difference, please send an mail to [email protected], so we may test to see if it is perhaps a defect within the software. Thanks.
It will begin from the task that failed. Unfortunately if your task is dependent on variables and values associated with the prior tasks, then it will fail due to those missing parameters. In that case, we suggest restarting the workflow over in it's entirety.
Switching environments is always a process as you have configured your scripts to run with one OS, and now switching to another OS means the possibility of changes made "behind the scenes". For example Win 2012 R2 might display a window with a different handle than it does on Win 2016 or 2019, which means that if you have an step that focuses on that window, it will now fail.
When these types of migrations are done, we highly recommend keeping the old server up and running as long as possible. This gives you a chance to install the software to the new environment, export jobs from the old to the new, and test each and every workflow/task in the new environment. This allows your production to not be hindered by the need to edit jobs.
Unfortunately using variables and/or constants within triggers is not supported at this time. It has been added as a feature enchancement however. The Feature request number is AM-15703. You can review the change logs when a new version of AutoMate is released, to verify if this feature has been implemented into that version.
We apologize for the inconvenience.
Is this occurring within task builder or when running on a schedule?
was this task ever working or is it a new task?
What version of AutoMate are you running? 11.1? 11.3? 11.5? etc...
Glad to hear you have resolved the issue!
If you review the windows application log for the agent running the workflows, do you find any errors regarding the agent failing?
Regarding your workaround, mapped drives must be mapped within the task in order to be recognized. There is a map drive action that you can add to your task, before the transfer takes place.
However, we recommend using the full UNC path instead of a mapped drive. This would be more reliable as the mapped/unmapped state of the drive will not come into effect.
We also have Azure actions, that are designed for file transfers. Here is more information on how to establish a session to begin your transfer:
and here are all the Azure actions available to you:
I took a look at our defect backlog and cannot find anything reported regarding the behavior you are experiencing.
Is it possible to download the trial version of 11.5 to see f you get the same results? You may do so by navigating to "my downloads" in the customer portal.
You mentioned you are able to access the location using a different account. Do you get an error when trying to use the AutoMate account?