ls ~/writing --tag=data-pipeline-reliability

[01]Writing · Tag

Articles tagged "data-pipeline-reliability".

$ tag --stat data-pipeline-reliability
Articles
4
Published
Jan→Feb 2026
Reading time
34 min
In series
1

Articles tagged data-pipeline-reliability

4 articles

8 min [bubble][bubble-list-field][data-integrity]

Why I stopped trusting Bubble.io's list fields and re-query the database instead

Bubble.io list fields don't auto-update when children point at parents. Re-query the database, write the actual list back. Here is the pattern.

Data Pipeline Reliability 4/4

re-query-database-platform-relationships--cover
The children point at the parent. The parent shows an empty list.

8 min [n8n][n8n-cloud][workflow-architecture]

n8n Cloud's 60-second timeout: the dispatcher-worker pattern that beats it

n8n Cloud caps Code nodes at 60 seconds and workflows at 40 minutes. Dispatcher-worker gives every chunk a fresh execution clock.

Data Pipeline Reliability 3/4

n8n-cloud-execution-cap-dispatcher-worker--cover
476 records never arrive, and the run still reports success.

9 min [n8n][bubble][idempotency]

Idempotent data pipelines: the natural-key fingerprint pattern

Make any n8n or Bubble.io pipeline safely re-runnable: hash a stable subset of source fields, store the fingerprint, check before every write.

Data Pipeline Reliability 2/4

idempotent-pipeline-natural-key-fingerprint--cover
Re-run the pipeline after a failure and the destination quietly doubles.

9 min [n8n][bubble][data-migration]

Silent failures: the bug class no tool catches in your data pipeline

4 silent failures I diagnosed in a Bubble + n8n migration: timeout truncation, one-sided relationships, mutable dedup keys, async webhook commits.

Data Pipeline Reliability 1/4

silent-failures-ai-built-pipelines--cover
Every node turns green, the run says completed, and a week later the rows are gone.

[02]Narrow it down

[03]Read in order

One series runs through this tag.

All articles