No-Code SaaS Automation Platform  ·  View 13 of 21  ·  Runtime

Trigger Ingestion

Push and poll as two different mechanisms with two different failure modes, not one abstraction.

Editable source SVG draw.io All views
Provider capability Push capable ~20% of catalogue Poll only ~80% of catalogue Own the lifecycle Subscription manager renew before expiry Cursor store watermark per conn Receive Signed endpoint p99 ack 250 ms Poll worker jittered interval Admit Deduplicate (conn, event id) Poison quarantine 30 d, typed reason Commit Trigger event log durable, 30 d Quiet-period alarm a silent source create, renew read since delivery watermark accepted unparseable liveness Trigger Ingestion — Push and Poll External / third party Application we own Data store Interface / broker Risk / gap Queue / topic Security / platform synchronous failure / alternate event / async A subscription that expired unnoticed is this platform's most common invisible failure, which is why renewal and the quiet-period alarm are components rather than settings. v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Subscription renewal is a component, not a setting. A subscription that expired unnoticed is this platform's most common invisible failure, and it presents as health.
  • A cursor advances only after the events it covers are durably committed. Advancing first is the single-line bug that produces a permanent, silent gap.
  • Poll intervals carry declared jitter so two million connections to one provider do not align on the minute boundary — a self-inflicted thundering herd against somebody else's quota.
  • The quiet-period alarm is wired off the event log, so the thing being watched is the absence of data rather than the health of the poller.

Assumptions

  • 2 M polled connections at an average 5-minute interval — roughly 6,700 provider polls/second, which is why Section 13 requires poll cost to be sub-linear in connection count.
  • Entitled poll intervals of 1, 5 and 15 minutes by plan; detection within one interval + 30 s at p95.
  • Where a provider supplies no event id, dedup falls back to a content fingerprint over a declared window and is documented as weaker.

Open

  • Core Architecture Question 1 is live on this view: the hybrid drawn here is two freshness models, two dedup mechanisms and two failure taxonomies behind one product promise.
◀  Critical Flow — One Run With a Rate Limit All views Step Lifecycle by Replay-Safety Class  ▶
Solution Architecture v1.0 · Amazon Web Services · Integration Platform Architecture · 2026-10 · 21 views13-trigger-ingestion