Platform
Worker architecture
A separate Tamanor worker runs scheduled read-only monitoring, token-expiry checks and webhook follow-up, each under a trusted tenant context and an account-level lease that prevents overlapping syncs.
One sync per account, safely
The worker acquires a short-lived account-level lease before syncing, so a scheduled run and a manual run can never collide. Reads are idempotent; each item is created once and updated in place on change.
The worker only reads. It never executes a moderation action; those flow exclusively through the approval queue.
Frequently asked questions
- Can two syncs run for the same account at once?
- No. An account-level lease guarantees a single active sync; the second run is skipped cleanly.