From 75444a9f1879c5702f9f2b8ad4a70a3a0e75871d Mon Sep 17 00:00:00 2001
From: gchaps <33642766+gchaps@users.noreply.github.com>
Date: Fri, 27 Sep 2019 09:31:00 -0700
Subject: [PATCH] [DOCS] Adds note to troubleshooting migration topic (#46815)

---
 docs/setup/upgrade/upgrade-migrations.asciidoc | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/setup/upgrade/upgrade-migrations.asciidoc b/docs/setup/upgrade/upgrade-migrations.asciidoc
index 4381bd2da3bd..81ff8344c4c5 100644
--- a/docs/setup/upgrade/upgrade-migrations.asciidoc
+++ b/docs/setup/upgrade/upgrade-migrations.asciidoc
@@ -46,7 +46,10 @@ The first instance that triggers saved object migrations will run the entire pro
 [[upgrade-migrations-rolling-back]]
 ==== Rolling back to a previous version of {kib}
 
-When rolling {kib} back to a previous version, point the `.kibana` alias to the appropriate {kib} index. When you have the previous version running again, delete the more recent `.kibana_N` index or indices so that future upgrades are based on the current {kib} index.
+When rolling {kib} back to a previous version, point the `.kibana` alias to 
+the appropriate {kib} index. When you have the previous version running again, 
+delete the more recent `.kibana_N` index or indices so that future upgrades are 
+based on the current {kib} index. You must restart {kib} to re-trigger the migration.
 
 WARNING: Rolling back to a previous {kib} version can result in saved object data loss if you had successfully upgraded and made changes to saved objects before rolling back.