include note that failed messages should have been ingested

Author: PhilBastian

docs/azure.md

@@ -24,6 +24,7 @@ If you encounter any issues running the steps below, try the [troubleshooting](#
    - All of the configured queues for your system should show here
    - For each row in the list of queues: if the queues exist, the status should be green `OK`. If the queues don't exist, i.e. there have never been any errors on that consumer, or if there is an issue connecting to the broker then the status will be red `Not ingesting`.
      - If the status is `Not ingesting`, the reason for this can be found in the log entries shown below the queue list.
+   - Any messages that existed in the error queues should now have been ingested, and will be shown in [Failed Messages](http://localhost:9090/#/failed-messages/all-failed-messages)
 
 ## Troubleshooting
 

docs/rabbit.md

@@ -28,6 +28,7 @@ If you encounter any issues running the steps below, try the [troubleshooting](#
    - All of the configured queues for your system should show here
    - For each row in the list of queues: if the queues exist, the status should be green `OK`. If the queues don't exist, i.e. there have never been any errors on that consumer, or if there is an issue connecting to the broker then the status will be red `Not ingesting`.
      - If the status is `Not ingesting`, the reason for this can be found in the log entries shown below the queue list.
+   - Any messages that existed in the error queues should now have been ingested, and will be shown in [Failed Messages](http://localhost:9090/#/failed-messages/all-failed-messages)
 
 ## Troubleshooting