Version 0.8.30

Fixed bug where error chain reaction would fire even if job was aborted. Aborted jobs, either due to shutdown or manual, should never fire a chain reaction action (and now they do not).
jhuckaby · Jun 30, 2019 · 943b667 · 943b667
1 parent e13a3a8
commit 943b667
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/lib/job.js b/lib/job.js
@@ -1461,7 +1461,8 @@ module.exports = Class.create({
 		if (job.chain && job.chain.length && (job.code == 0)) {
 			this.chainReaction( job, job.chain );
 		}
-		else if (job.chain_error && job.chain_error.length && (job.code != 0)) {
+		else if (job.chain_error && job.chain_error.length && (job.code != 0) && !job.abort_reason) {
+			// only fire error chain reaction if job was not manually aborted (job.abort_reason)
 			this.chainReaction( job, job.chain_error );
 		}
 

diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "Cronicle",
-	"version": "0.8.29",
+	"version": "0.8.30",
 	"description": "A simple, distributed task scheduler and runner with a web based UI.",
 	"author": "Joseph Huckaby <jhuckaby@gmail.com>",
 	"homepage": "https://github.com/jhuckaby/Cronicle",