fix: handle null input in scheduled TypeScript cron runs - #18
Merged
Conversation
The v1 TypeScript SDK passes null through to the task when a cron run carries no input, so the released scheduled template failed on every cron firing. The task now falls back to an empty message when input is null. The examples e2e only exercised the manual-run trigger, which always supplies input, so a cron firing was never tested. The TypeScript scheduled example now waits for a cron run and asserts it completed. Python and Go stop at manual-run validation because their SDKs fill a missing input with defaults.
gregfurman
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The v1 TypeScript SDK passes null through to the task when a cron run carries no input, so the released scheduled template failed on every cron firing. The task now falls back to an empty message when input is null.
The examples e2e only exercised the manual-run trigger, which always supplies input, so a cron firing was never tested. The TypeScript scheduled example now waits for a cron run and asserts it completed. Python and Go stop at manual-run validation because their SDKs fill a missing input with defaults.
Type of change
What's Changed
Checklist
Changes have been:
Testing
The full script ran locally against a fresh hatchet-lite stack. All six examples passed and the TypeScript cron wait completed. Before the fix, the same wait reproduced the TypeError on every firing.
🤖 AI Disclosure
I acknowledge that an LLM was used in the creation of this Pull Request, in accordance with Hatchet's AI_POLICY.md.
Details: Claude Code (claude-fable-5) wrote the e2e cron assertions.