docs(general): warn about empty TZ env breaking internal cron scheduler#643
Open
singhvishalkr wants to merge 1 commit intodirectus:mainfrom
Open
docs(general): warn about empty TZ env breaking internal cron scheduler#643singhvishalkr wants to merge 1 commit intodirectus:mainfrom
singhvishalkr wants to merge 1 commit intodirectus:mainfrom
Conversation
|
@singhvishalkr is attempting to deploy a commit to the Directus Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
Fixes #512.
Tracing the
CronError: ERROR: You specified an invalid datereported in Dec 2025 ended up exactly where @the-other-dev landed on the thread: Directus 11.13 swappednode-scheduleforcron, andcronreads the processTZenv var (whichnode-scheduleignored). SettingTZ=""(empty string, which is what some orchestrators like UnRAID emit by default) now crashes the telemetry scheduler at startup before anything else can run, and the same would affect TUS cleanup and anyscheduleflow operations.ComfortablyCoding asked on the issue to document this rather than change defaults, so I added a single warning callout in
configuration/general.mdright after the main env-var table that tells people to either leaveTZunset or set it to a valid IANA zone.Only text change; no variable additions.