Trigger.dev was weighed for schedules, retries, and task-level idempotency. It was not implemented because the database-to-service handoff still needed an outbox and the documented idempotency lifecycle was weaker than permanent event identity.
- What worked
- Its managed TypeScript task model appeared approachable for the existing application.
- What got in the way
- Finite idempotency retention and failed-run key behavior did not fully satisfy the required long-term duplicate protection.
