influxdata/influxdb · error · PluginError
invalid cron syntax
Error message
invalid cron syntax: {0} What it means
PluginError::InvalidCronSyntax, wrapping cron::error::Error when a trigger's cron schedule string cannot be parsed by the cron crate; raised when creating or updating a scheduled trigger with a malformed cron expression.
Solutions
- Fix the cron expression before passing it to trigger creation
- Test the expression with the cron crate's parser or an equivalent validator
- Use a supported 5/6/7-field cron format accepted by the `cron` crate
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at influxdb3_processing_engine/src/plugins.rs:56 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of influxdata/influxdb@06200ef96b (2026-09-19).
Data as JSON: /api/errors/f2aeaf48e8ef0ffe.
Report an issue: GitHub.
Appendix: source
Thrown at influxdb3_processing_engine/src/plugins.rs:56
#[error("couldn't find db")]
MissingDb,
#[error(transparent)]
PyError(#[from] pyo3::PyErr),
#[error(transparent)]
WriteBufferError(#[from] write_buffer::Error),
#[error(transparent)]
AnyhowError(#[from] anyhow::Error),
#[error("reading plugin file: {0}")]
ReadPluginError(#[from] std::io::Error),
#[error("error executing plugin: {0}")]
PluginExecutionError(#[from] influxdb3_py_api::error::ExecutePluginError),
#[error("invalid cron syntax: {0}")]
InvalidCronSyntax(#[from] cron::error::Error),
#[error("cron schedule never triggers: {0}")]
CronScheduleNeverTriggers(String),
#[error("non-schedule plugin with schedule trigger: {0}")]
NonSchedulePluginWithScheduleTrigger(String),
#[error("error fetching plugin from repository: {0} {1}")]
FetchingFromRepository(reqwest::StatusCode, String),
#[error(
"plugin installation is disabled; plugins must already exist in the configured plugin directory"
)]
PluginInstallationDisabled,
#[error("Join error, please report: {0}")]
JoinError(#[from] tokio::task::JoinError),View on GitHub (pinned to 06200ef96b)