From b0c23f4a8d25d548c39d8a16c81348079c6d8351 Mon Sep 17 00:00:00 2001 From: rob Date: Mon, 29 Jun 2026 09:04:55 +0000 Subject: [PATCH] Migrated from GitLab wiki --- Order%2FOrder-and-Shipment-LifeCycle.-.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 Order%2FOrder-and-Shipment-LifeCycle.-.md diff --git a/Order%2FOrder-and-Shipment-LifeCycle.-.md b/Order%2FOrder-and-Shipment-LifeCycle.-.md new file mode 100644 index 0000000..6534801 --- /dev/null +++ b/Order%2FOrder-and-Shipment-LifeCycle.-.md @@ -0,0 +1,19 @@ +![eStack-Order-Shipment LifeCycle.png](uploads/5b94c2884a67c235c6b6954aef311e4c/eStack-Order-Shipment_LifeCycle.png){width=2349 height=1380} + +**CRON JOB TO PROCESS ORDERS and SHIPMENTS** + +The way eStack run cron jobs, the job will be pushed to supervisor job management service and they start getting executed one by one. So you need to have good understanding of Supervisord as well, if you need to make any of your new worker for shipment. + +``` +/estack$ bin/pms3 worker ship +``` + +This will start the shipment worker which will start looking for jobs queued for this worker. + +To check this, you must have two terminals opened, One is running with the worker and another one to push the jobs by executing some commands as like below. + +``` +bin/pms3 shipment sweep +``` + +This command will push jobs for each instance in the queue and worker will start processing those jobs, based on this jobs it clean up any shipments that should have been marked shipped but weren't. \ No newline at end of file