n8n: add bounded retries and timeout to WF1's Fleet Ops callback
Vehicle Return Orchestration had no explicit timeout and Retry On Fail disabled on its outbound HTTP call, a gap against the acceptance checklist's timeouts/bounded-retries requirement. Fixed live (3 tries, 1000ms wait, 15s timeout, matching WF2's existing convention) and synced the repo definition + manifest checksum.
This commit is contained in:
@@ -17,7 +17,8 @@ credential values are never embedded; nodes reference named n8n credentials inst
|
||||
| Live workflow ID | `mobilityops-return-processing` |
|
||||
| Active status (as of 2026-08-04) | Active / Published |
|
||||
| Error Workflow | `Fleet Ops — Workflow Error Handler` (wired) |
|
||||
| Checksum (sha256) | `e13a3087269fc97019a7adf6c6a6a4ee4bd354c2dd7167d4966d4753a48e970e` |
|
||||
| Timeouts / bounded retries | `Record follow-up` HTTP node: 15s timeout, retry on fail (3 tries, 1000ms wait) |
|
||||
| Checksum (sha256) | `a6f399dd77a7203dec7c0ac95e8540abf55f2703da519e06f1c37f2e1220f609` |
|
||||
|
||||
## 2. Fleet Ops — Scheduled Data Quality Scan
|
||||
|
||||
|
||||
@@ -51,7 +51,9 @@
|
||||
"contentType": "raw",
|
||||
"rawContentType": "application/json",
|
||||
"body": "={{JSON.stringify($json)}}",
|
||||
"options": {}
|
||||
"options": {
|
||||
"timeout": 15000
|
||||
}
|
||||
},
|
||||
"id": "callback-node",
|
||||
"name": "Record follow-up",
|
||||
@@ -62,8 +64,10 @@
|
||||
"httpHeaderAuth": {
|
||||
"name": "Fleet Ops Service Token"
|
||||
}
|
||||
}
|
||||
},
|
||||
},
|
||||
"retryOnFail": true,
|
||||
"maxTries": 3,
|
||||
"waitBetweenTries": 1000
|
||||
{
|
||||
"parameters": {
|
||||
"respondWith": "json",
|
||||
|
||||
Reference in New Issue
Block a user