Scheduled build cannot be parsed: invalid date format – time zone conversion in Bamboo logs

Bamboo Scheduled Builds: Invalid Date Format Errors and Log Time Zone Reconciliation

Short answer: Bamboo does not provide a per-plan time zone setting for scheduled builds or log timestamps. Schedule evaluation and log rendering follow the server-level time zone. The Scheduled build cannot be parsed: invalid date format error is almost always a malformed cron expression or unsupported schedule syntax, not a time zone conversion issue.

Confirmed facts vs. likely explanation

Confirmed: Bamboo uses the time zone configured in Administration > System settings for schedule evaluation and log rendering. Changing that setting is a deployment-wide change; it shifts every existing cron schedule and does not create per-plan overrides.

Likely: The parse error originates from an invalid schedule string. Bamboo expects standard cron syntax (Quartz-style in many versions) and does not accept arbitrary date formats or time zone offsets inside the expression.

Uncertainty: The premise that logs always default to UTC is not guaranteed across all Bamboo versions. Timestamp behavior varies by release and server configuration, so inspect a live build log before assuming UTC.

Steps for this case

1. Open Administration > System settings and record the server time zone.
2. Trigger a build and compare the first log timestamp with the server clock to determine the actual log time zone for your instance.
3. Create a throwaway plan with a known-good schedule (for example, 0 0 12 * * ?) and a deliberately malformed one to confirm the parser rejects syntax, not time zones.
4. Check your Bamboo version’s release notes for changes to schedule parsing or log timestamp formatting.

Recommended workflow for multi-region teams

Treat the Bamboo server time zone as a deployment-wide constant. Standardize all schedules on that zone—ideally UTC—and convert timestamps to local time in downstream dashboards, log aggregators, or reporting scripts. Do not attempt undocumented per-plan time zone overrides; they may break on upgrade and are not supported by the schedule persistence or trigger evaluation layers.

Impact of a hypothetical per-plan time zone

If Bamboo were to add per-plan time zones, it would require coordinated changes to schedule persistence, trigger evaluation, and log rendering. Existing schedules would remain tied to the server time zone, and any migration would risk misaligned triggers or log parsing errors. Until such a feature exists, there is no native way to align log timestamps with a plan-specific local schedule time.

One diagnostic detail needed

Please provide the exact schedule expression that triggers the parse error. If it is syntactically valid, the issue may be version-specific parser behavior; if it is malformed, the fix is to correct the cron string.