diff --git a/README.adoc b/README.adoc
index 5f64ea16..0ceb2707 100644
--- a/README.adoc
+++ b/README.adoc
@@ -1020,12 +1020,21 @@ image::{jenkins-root-docs}/blue_6.png[caption="Step 6: ", title="The build is in
 {nbsp}
 {nbsp}
 
-image::{jenkins-root-docs}/blue_6.png[caption="Step 7: ", title="The pipeline is done!"]
+image::{jenkins-root-docs}/blue_7.png[caption="Step 7: ", title="The pipeline is done!"]
 
 {nbsp}
 {nbsp}
 
 
+IMPORTANT: There is no possibility of restarting pipeline from specific stage, after failure. Please
+check out this https://issues.jenkins-ci.org/browse/JENKINS-33846[issue] for more information
+
+WARNING: Currently there is no way to introduce manual steps in a performant way. Jenkins is
+blocking an executor when manual step is required. That means that you'll run out of executors
+pretty fast. You can check out this https://issues.jenkins-ci.org/browse/JENKINS-36235[issue] for
+and this http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei[StackOverflow question]
+for more information.
+
 === Optional steps
 
 [[jenkins_optional]] All the steps below are not necessary to run the demo. They are needed only
diff --git a/docs/JENKINS.adoc b/docs/JENKINS.adoc
index 8820c6fa..4ce6e101 100644
--- a/docs/JENKINS.adoc
+++ b/docs/JENKINS.adoc
@@ -290,12 +290,21 @@ image::{jenkins-root-docs}/blue_6.png[caption="Step 6: ", title="The build is in
 {nbsp}
 {nbsp}
 
-image::{jenkins-root-docs}/blue_6.png[caption="Step 7: ", title="The pipeline is done!"]
+image::{jenkins-root-docs}/blue_7.png[caption="Step 7: ", title="The pipeline is done!"]
 
 {nbsp}
 {nbsp}
 
 
+IMPORTANT: There is no possibility of restarting pipeline from specific stage, after failure. Please
+check out this https://issues.jenkins-ci.org/browse/JENKINS-33846[issue] for more information
+
+WARNING: Currently there is no way to introduce manual steps in a performant way. Jenkins is
+blocking an executor when manual step is required. That means that you'll run out of executors
+pretty fast. You can check out this https://issues.jenkins-ci.org/browse/JENKINS-36235[issue] for
+and this http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei[StackOverflow question]
+for more information.
+
 === Optional steps
 
 [[jenkins_optional]] All the steps below are not necessary to run the demo. They are needed only
diff --git a/docs/spring-cloud-pipelines.html b/docs/spring-cloud-pipelines.html
index 0f7ab9d3..95eaa90b 100644
--- a/docs/spring-cloud-pipelines.html
+++ b/docs/spring-cloud-pipelines.html
@@ -2441,7 +2441,7 @@ <h3 id="_declarative_pipeline_blue_ocean">Declarative pipeline &amp; Blue Ocean<
 </div>
 <div class="imageblock">
 <div class="content">
-<img src="img/jenkins/blue_6.png" alt="blue 6">
+<img src="img/jenkins/blue_7.png" alt="blue 7">
 </div>
 <div class="title">Step 7: The pipeline is done!</div>
 </div>
@@ -2449,6 +2449,35 @@ <h3 id="_declarative_pipeline_blue_ocean">Declarative pipeline &amp; Blue Ocean<
 <p>&#160;
 &#160;</p>
 </div>
+<div class="admonitionblock important">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Important</div>
+</td>
+<td class="content">
+There is no possibility of restarting pipeline from specific stage, after failure. Please
+check out this <a href="https://issues.jenkins-ci.org/browse/JENKINS-33846">issue</a> for more information
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<div class="title">Warning</div>
+</td>
+<td class="content">
+Currently there is no way to introduce manual steps in a performant way. Jenkins is
+blocking an executor when manual step is required. That means that you&#8217;ll run out of executors
+pretty fast. You can check out this <a href="https://issues.jenkins-ci.org/browse/JENKINS-36235">issue</a> for
+and this <a href="http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei">StackOverflow question</a>
+for more information.
+</td>
+</tr>
+</table>
+</div>
 </div>
 <div class="sect2">
 <h3 id="_optional_steps">Optional steps</h3>
diff --git a/jenkins/README.adoc b/jenkins/README.adoc
index 1b6a2603..dcdd5f17 100644
--- a/jenkins/README.adoc
+++ b/jenkins/README.adoc
@@ -294,12 +294,21 @@ image::{jenkins-root-docs}/blue_6.png[caption="Step 6: ", title="The build is in
 {nbsp}
 {nbsp}
 
-image::{jenkins-root-docs}/blue_6.png[caption="Step 7: ", title="The pipeline is done!"]
+image::{jenkins-root-docs}/blue_7.png[caption="Step 7: ", title="The pipeline is done!"]
 
 {nbsp}
 {nbsp}
 
 
+IMPORTANT: There is no possibility of restarting pipeline from specific stage, after failure. Please
+check out this https://issues.jenkins-ci.org/browse/JENKINS-33846[issue] for more information
+
+WARNING: Currently there is no way to introduce manual steps in a performant way. Jenkins is
+blocking an executor when manual step is required. That means that you'll run out of executors
+pretty fast. You can check out this https://issues.jenkins-ci.org/browse/JENKINS-36235[issue] for
+and this http://stackoverflow.com/questions/42561241/how-to-wait-for-user-input-in-a-declarative-pipeline-without-blocking-a-heavywei[StackOverflow question]
+for more information.
+
 === Optional steps
 
 [[jenkins_optional]] All the steps below are not necessary to run the demo. They are needed only