diff --git a/3387a4be54016ac6efdfb2c432cc85b790525063 b/3387a4be54016ac6efdfb2c432cc85b790525063
index d7d363a..01d9216 100644
--- a/3387a4be54016ac6efdfb2c432cc85b790525063
+++ b/3387a4be54016ac6efdfb2c432cc85b790525063
@@ -440,6 +440,30 @@
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
       "unresolved": false
     },
+    {
+      "key": {
+        "uuid": "7ffa3b31_666cc69b",
+        "filename": "specs/splitting-service-on-API-and-worker.rst",
+        "patchSetId": 6
+      },
+      "lineNbr": 86,
+      "author": {
+        "id": 18653
+      },
+      "writtenOn": "2017-04-21T08:22:18Z",
+      "side": 1,
+      "message": "More seriously, I think it\u0027s good to have a safety timeout mechanism in place to avoid having to resort to manually update the database to unblock stale tasks, that the operator might dislike more than a slower response.\n\nAlso please note if we adopt single timeout for the whole introspection procedure, manually triggered introspections will detect an outage within the timeout, including node boot, as we derive it from the started_at timestamp.\n\nDiscoveries will have longer time to spend in the processing state before declared stale\u0026timeout.\n\nAnother approach is to allow abort to happen in any active state.",
+      "parentUuid": "7ffa3b31_cc4e3737",
+      "range": {
+        "startLine": 86,
+        "startChar": 15,
+        "endLine": 86,
+        "endChar": 37
+      },
+      "revId": "3387a4be54016ac6efdfb2c432cc85b790525063",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
+      "unresolved": false
+    },
     {
       "key": {
         "uuid": "7ffa3b31_59a316b3",