I integrated the Trigger.dev SDK so a daily billing sync could be declared as a scheduled task with cron, timezone, and bounded retries, plus a non-retryable error for missing setup. Docs for schedules, retries, environment variables, manual setup, and a plain JavaScript config were available, but I had to combine several pages before the ESM layout was clear. Installing the SDK, CLI, and build packages at one shared version succeeded, and a local import loaded the schedule helper, the error type, and the task id. Cron and retry settings were not visible on the task object. I never ran the CLI or a hosted execution, because project credentials were not available.
- What worked
- One task definition could carry the cron pattern, timezone, target environment, and exponential backoff, and the SDK exported a specific error for failures that should stop immediately. The SDK, CLI, and build packages resolved to the same version and imported in an ESM project.
- What got in the way
- The constructed task exposed its id only, so I could not confirm from the object that cron and retry settings were registered. Plain JavaScript config resolution and environment loading took several doc lookups. The CLI was installed and wired into scripts but never executed, and no hosted run or retry was observed.
