ZZZ Digital Lab

Back to n8n workflow hardening

Sample client deliverable: $25 bounded n8n diagnosis

SYNTHETIC CASE. Engineering with AI coding tools, tests and written handoff. No n8n instance or production API was accessed. The $25 tier covers one supplied workflow export, representative synthetic events, findings, a repair plan and a conditional estimate. It excludes live-instance inspection and implementation. It is narrower than the separate full workflow diagnostic.

Finding Synthetic evidence Risk Fix plan
No retry/backoff or time bounds HTTP node lacks retry and timeout settings Transient loss or hung executions Max 3 attempts, fixed 1-second delay, 5-second header timeout, workflow limit
Duplicate processing Baseline emits all 3 events including one repeat Repeated business side effects Stable event identity; bounded validation; atomic idempotent receiver contract
No error workflow No error reference or error handler Failure invisible to operators Separate Error Trigger workflow and safe incident sink
Unbounded cycle Send node routes back to processing Runaway processing Acyclic graph and max 50 events per envelope
Inline secret pattern Fake synthetic Authorization marker in parameters Unsafe configuration practice Credential references, configured by the client locally
No durable failure record No dead-letter branch Lost context and unsafe retries Persist original linked event by stable dead-letter key, fail visibly, reconcile before closing

Static result: 14 findings before, 0 after. All 29 offline tests pass, including success, repeated input, transient failure, permanent failure, lost acknowledgement, dead-letter failure and recovery. These prove the local checks and fake-receiver contract only. Native n8n behavior and remote services remain unverified.

Recommended acceptance: import into a disposable client-controlled instance; bind placeholder credential references and error workflow; demonstrate automatic success/duplicate/failure/recovery runs against a staging receiver with atomic key storage; inspect native retry timing, linked original events, durable dead-letter persistence, failure signals and retention. Agree webhook acknowledgement and proxy timeouts. A header alone cannot guarantee exactly-once business effects.

Conditional repair estimate: 3-6 engineering hours for one similar bounded workflow and one primary failure pattern, plus 1-2 hours for client-controlled staging acceptance. Example fixed repair quote $350 after confirming node versions, API contracts and access. Unknown migrations, building a durable receiving service, infrastructure changes, 24/7 monitoring and third-party availability are excluded. Estimate and quote are proposed terms, not measured production turnaround.

See HANDOFF.md for a concrete run checklist, retained evidence, recovery and rollback.