Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


DJacobsen
2017-01-06T16:46:38Z
I have an email notification that runs on Job Error...

Job -> Flow -> On error -> Run Notification 'Error Email'

I am trying to include the Task Name that encountered the error, the Stdout, StrErr, ExitCode, and ExitCodeDesc. I was able to include this information when the notification was ran on the Task Flow with:

[{TASK(PrevTask,StdOut)}]

But is there a way to get the information when the notification is ran from the Job flow?
Sponsor
Forum information
thomas
2017-01-07T10:58:15Z
I use this:

Job: {JOB(Active|Name)}
Task: {TASK(PrevTask|Name)}
Exit code: {TASK(PrevTask|ExitCode)}
Errormessage: {TASK(PrevTask,StdErr)}

Thomas
DJacobsen
2017-01-09T16:02:53Z
Originally Posted by: thomas 

I use this:

Job: {JOB(Active|Name)}
Task: {TASK(PrevTask|Name)}
Exit code: {TASK(PrevTask|ExitCode)}
Errormessage: {TASK(PrevTask,StdErr)}

Thomas



That is what we are using as well, but if the Notification is sent from a Job level flow then we get

Task Name: [Task does not exist or is not selected.]



thomas
2017-01-09T20:51:47Z
That's strange. This works for us when we set it on job level:
Job - flow - onerror - send notification. In the notification (emial) we have what I posted previously.
Support
2017-01-11T08:08:56Z
Please download and re-install the latest version. I recall a bug here.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
DJacobsen
2017-01-11T16:18:35Z
Thanks Henrik, that worked. We were still on 8.2.2. Updating the server to 8.2.3 worked, though oddly when clients were opened they were not prompted to update from 8.2.2 to 8.2.3. Even when running Check Updates on the client it would return saying that they were on the latest version.

We had to manually download the 8.2.3 installer from the website and then install it in order to update the clients.
Support
2017-01-12T07:43:30Z
Maybe you were using different versions of Client and Server?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
DJacobsen
2017-01-12T14:02:14Z
Originally Posted by: Support 

Maybe you were using different versions of Client and Server?



We were. The server was updated to 8.2.3. The clients were still on 8.2.2. I expected the clients to be prompted to update to the latest version when they attempted to connect to a server at a higher version then they are. Is that not the expected process?


Support
2017-01-13T13:22:53Z
As I recall it we check server version. But generally you should use same or newer version of client. Older can become a problem.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top