Hi Henrik,

It seems {Task|Prev|ExitCode} isn't lexically bound to the task we're referencing.
The alternative, {Task|TaskGuidGoesHere|ExitCode} is bad because:
1. It's hard to read/audit.
2. When cloning a job, the tasks cloned get assigned new guid's, but the variables don't get replaced with new guids as well. (VERY RISKY!!)

Do you think you could improve the VisualCron variables so that {Task|Prev|ExitCode} is lexically bound to the task we're referring to? I don't see how its helpful to output a random result from "the last task that executed anywhere on this VisualCron server". It seems like a huge bug to me. Anybody like us who is firing off jobs every second will likely face this issue, and may not even realize it.

PrevTask should always be unique and not mixed up with anything else. Can you reproduce this in any way?

---

PrevTask should always be unique and not mixed up with anything else. Can you reproduce this in any way?

How about I forward support@visualcron.com an alert I just received with the email template I configured?

This is 100% reproducible. It's just a race condition, so all that matters is that the "previous task" changes. To prove this out, you need two or more frequently running tasks.

Hi Henrik,

Attached the repro - had trouble sending it to support@visualcron.com via email   VisualCronReproFull.zip (9kb) downloaded 36 time(s).