476ebb957aebb1a7f20ea71301e894c5422bd57e
hiram
  Wed Apr 29 21:41:01 2026 -0700
subtle timing issue resolved and minor bugs fixed refs #31811

diff --git src/hg/utils/otto/userRequests/README.txt src/hg/utils/otto/userRequests/README.txt
index abbd1c7db95..f5f06072a16 100644
--- src/hg/utils/otto/userRequests/README.txt
+++ src/hg/utils/otto/userRequests/README.txt
@@ -1,21 +1,21 @@
 The 'status' field in the ottoRequest table maintains state:
 
   0 == request has been received by API (set by API)
   1 == request has been acknowledged by ottoRequest.py (set by ottoRequest.py)
   2 == galaxy jobs have been started (set by ottoRequestAlign.sh)
-  3 == galaxy jobs have completed (set by workflowMonitor.sh)
+  3 == galaxy jobs have completed, download started (set by workflowMonitor.sh)
   4 == download from galaxy has taken place and track files have been created
          (set by ottoRequestWatch.sh)
   5 == symlinks for tracks are in place, ready to push files
          (set by ottoRequestWatch.sh)
   6 == push of files is complete (set by ottoRequestPush.sh)
   7 == error condition - some error has taken place, set by any script
   8 == final email notification has been sent, galaxy workflow
        has been deleted, process is complete (set by ottoRequestWatch.sh)
 
 Method of operation:
 
 ############################################################################
 ###  1.
 User makes request via the liftRequest.html page.