Automation thatplays by the rules.

Meta expects an instant response to every webhook — and retries or disables endpoints that are slow.

Each webhook is signature-checked in constant time, de-duplicated, stored and queued before responding. All real work happens later in the worker.

Every Instagram account has its own call budget. Exceed it and the account is throttled.

Each account gets an atomic token bucket in Redis, deliberately set below Meta's ceiling and counted in API calls rather than messages.

A single viral post can generate thousands of events and starve every other customer.

A custom scheduler claims accounts one at a time with priority tiers, so rewards and paid users go first and no account can monopolise the workers. A load test verifies fairness, limits and idempotency.

Messaging windows and one-reply-per-comment rules can expire between queueing a job and running it.

Guards run at execution, not enqueue: the 24-hour window, the private-reply window, one reply per comment and one response per user per post — backed by unique database keys.

Tokens expire, networks blip and permissions get revoked.

Errors are classified as transient, permanent or auth. Transient ones back off and retry, auth failures prompt a reconnect, tokens refresh automatically before expiry and are stored encrypted.