From 938e2e3ab9cc297dcc3cbdac922c0d38ea27829e Mon Sep 17 00:00:00 2001 From: Joshua Baskaran Date: Wed, 29 Nov 2023 13:56:17 +0100 Subject: [PATCH] Fixed whitespace issue which caused the last 4 points to render as 8 - 10. --- docs/services/verify.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/services/verify.md b/docs/services/verify.md index a0f18fa..1285ede 100644 --- a/docs/services/verify.md +++ b/docs/services/verify.md @@ -24,14 +24,14 @@ If this fails an error will be written to the logs. If this fails an error will be written to the logs. 7. If the `re_verify` boolean is not set in the RabbitMQ message, the message processing ends here, and continues with the next message. Otherwise the processing continues with verification: - 1. A verification message is created, and validated against the `ingestion-accession-request` schema. - If this fails an error will be written to the logs. - 2. The file is marked as *verified* in the database (*COMPLETED* if you are using database schema <= `3`). - If this fails an error will be written to the logs. - 3. The verification message created in step 7.1 is sent to the `verified` queue. - If this fails an error will be written to the logs. - 4. The original RabbitMQ message is ACKed. - If this fails an error is written to the logs, but processing continues to the next step. + 1. A verification message is created, and validated against the `ingestion-accession-request` schema. + If this fails an error will be written to the logs. + 2. The file is marked as *verified* in the database (*COMPLETED* if you are using database schema <= `3`). + If this fails an error will be written to the logs. + 3. The verification message created in step 7.1 is sent to the `verified` queue. + If this fails an error will be written to the logs. + 4. The original RabbitMQ message is ACKed. + If this fails an error is written to the logs, but processing continues to the next step. ## Communication