ANTIGRAVITY LABJP
TAG

idempotency

13 articles
Back to all tags
Related:
Antigravity6antigravity5agents4production3reliability3multi-agent2managed-agents2batch2operations2Managed Agents2scheduled-execution2cost management1
Agents/2026-07-06Advanced

When Parallel Agents Ran the Same Task Twice and Quietly Doubled the Bill — Field Notes on Measuring and Stopping Duplicates

The bill for our parallel agents came in about 1.9x higher than expected — because multiple workers were running the same task twice. These are field notes on measuring the duplication, stopping it with idempotency keys, and attributing cost per task.

Agents/2026-07-06Advanced

Never Miss a Managed Agent Completion: Pairing a Serverless Receiver with Polling Reconciliation

A cloud Managed Agent can finish while you are not watching, and the webhook that should tell you can quietly fail. Here is a serverless receiver on Cloudflare Workers paired with polling reconciliation, and a state machine that recovers every completion within minutes.

Agents/2026-06-22Advanced

Your Antigravity Custom Tools Don't Break by Design — They Break on Re-execution: Field Notes on Idempotency and Error Contracts

Once you add a custom tool to an Antigravity agent, the real production problem is re-execution and duplicated side effects. Here are the idempotency keys, error contracts, health gates, and tool-sprawl checks that actually held up in practice.

Agents/2026-06-18Advanced

When Your Antigravity Agent's Usage Ledger Quietly Drifts From Stripe's Bill — Field Notes on Idempotency, Late Events, and Reconciliation

Usage-based billing for Antigravity agents fails silently when your internal usage ledger and Stripe's Meter Events aggregation drift apart. Field notes on idempotency keys, absorbing late events, the 35-day window, and a daily reconciliation job.

Agents/2026-06-17Advanced

Making Managed Agent Batches Safe to Re-run: Idempotency and Checkpoints

Running overnight batches on the Antigravity 2.0 Managed Agents API makes recovery from partial failure unavoidable. Starting from a duplicate-post incident, I share the implementation of idempotency keys, a checkpoint store, and resume logic, with real numbers from solo operations.

Integrations/2026-06-16Advanced

When a Cloud Nightly Batch Drifts From Yesterday's Result — An Input Contract and Snapshot Design for Reproducibility

When you push a batch to a cloud ephemeral worker via the Managed Agents API, the environment assumptions you took for granted locally vanish. Here is a three-layer design — environment snapshot, input contract, seed pinning — that keeps the same input producing the same result.

Integrations/2026-06-14Advanced

Trusting Temporal Workflows in Production — Field Notes on Idempotency, Retry Triage, and Saga Compensation

Practical notes from running Temporal as a production backend: how to make activities idempotent for real, where to draw the line between retryable and fatal errors, how to keep Saga compensation from firing twice, and how to make it all observable—built with Antigravity in the loop.

Agents/2026-06-14Advanced

Making My Managed Agents Batch Survive a Crash Without Redoing Everything

Running a 200-item batch on the Managed Agents API kept torching tokens, because every mid-run failure restarted from item one. Here is the checkpoint-and-idempotency design I added so the batch resumes from where it died.

Agents/2026-06-13Advanced

When a Scheduled Agent Runs Twice — Designing for Idempotency Against Overlap and Retry

A scheduled agent can do the same work twice when the next run triggers before the last one finishes. Here is a design with an overlap lock and an idempotency guard that survives mid-run failures, drawn from a double-publish incident I ran into in production.

Agents/2026-06-13Advanced

Building Idempotent Scheduled Agents with the Antigravity SDK

Scheduling an Antigravity SDK agent is almost a one-liner. The hard part is making it idempotent — so a double trigger never runs the job twice, a crash never drops a day, and the result always converges to one. Here is how I build idempotent scheduled agents, learned from the maintenance jobs I run as an indie developer.

Agents/2026-05-24Advanced

Designing Antigravity Agents That Survive Multi-Hour Batches — A 4-Layer Durability Pattern From the Trenches

Long-running Antigravity batch agents will fail somewhere. After running them against the operations of an indie app business, I distilled four durability layers — checkpoint granularity, persistence choice, idempotent restore, and context summarization — into a single, opinionated design memo with working code and real cost numbers.

App Dev/2026-05-03Advanced

Building Idempotency Keys and Dedupe Stores in TypeScript with Antigravity

A production guide to designing idempotency keys and dedupe stores in TypeScript with Antigravity — covering Stripe webhook retries, Temporal replays, and the Cloudflare KV / Redis / Postgres trade-offs you actually need to choose between.