diff --git a/README.md b/README.md
index 143e268..b33251b 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,7 @@
+> | :exclamation:  Breaking changes in Obsidian 1.6.3 causing a minor issue - no solution yet|
+> |----------------------------------------------|
+> |[More details](README.notice.for.Obsidian.1.6.3.md)| 
+
 > | :exclamation:  Breaking changes in Obsidian 1.6.0 (and newer) - update the plugin to 2.1.9 or newer|
 > |----------------------------------------------|
 > |[More details](README.notice.for.Obsidian.1.6.0.md)| 
diff --git a/README.notice.for.Obsidian.1.6.3.md b/README.notice.for.Obsidian.1.6.3.md
new file mode 100644
index 0000000..5ba23f2
--- /dev/null
+++ b/README.notice.for.Obsidian.1.6.3.md
@@ -0,0 +1,9 @@
+> | :exclamation:  Breaking changes in Obsidian 1.6.3 causing a minor issue - no solution yet|
+> |----------------------------------------------|
+>
+> Obsidian team introduced yet another breaking change in 1.6.3 probably related to plugin's lifecycle or File Explorer module lifecycle.
+> In result the custom sort order is not applied automatically and manual (re)application is needed via ribbon click of via 'sort on' command after
+> app reload or vault reload.
+> 
+> For more details of the observed misbehavior (of not updated plugin) you can go to [#147](https://github.com/SebastianMC/obsidian-custom-sort/issues/147)
+