From 8b30743d0a5e44c7673f90b4509989f8f35a7cb3 Mon Sep 17 00:00:00 2001
From: Renat Akhmerov <renat.akhmerov@gmail.com>
Date: Wed, 21 Mar 2018 11:44:05 +0700
Subject: [PATCH] Add a release note for the 'pause' command fix

Change-Id: Ia609cb319a01b3685d91515c8d9d81e3006a001e
Related-Bug: #1714054
---
 .../notes/fix_pause_command-58294f613488511c.yaml        | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 releasenotes/notes/fix_pause_command-58294f613488511c.yaml

diff --git a/releasenotes/notes/fix_pause_command-58294f613488511c.yaml b/releasenotes/notes/fix_pause_command-58294f613488511c.yaml
new file mode 100644
index 000000000..514c1e3b7
--- /dev/null
+++ b/releasenotes/notes/fix_pause_command-58294f613488511c.yaml
@@ -0,0 +1,9 @@
+---
+fixes:
+  - Fixed the logic of the 'pause' command. Before the fix Mistral wouldn't
+    run any commands specified in 'on-success', 'on-error' and 'on-complete'
+    clauses following after the 'pause' command when a workflow was resumed
+    after it. Now it works as expected. If Mistral encounters 'pause' in the
+    list of commands it saves all commands following after it to the special
+    backlog storage and when/if the workflow is later resumed it checks that
+    storage and runs commands from it first.