Skip to main content
Use this page for errors returned when triggering Bolt schedules programmatically from the API, Python SDK, CLI, or a CI/CD pipeline.

​
Schedule name (’…’) does not exist in database

Your pipeline or script is triggering the schedule by its display name, but the schedule is identified by its slug. Since the June 2026 slug release, every new schedule gets a unique slug (for example flowing-pachy-wyy4fs), and the schedule_name parameter in the API and Python SDK is a deprecated alias that expects a slug. Schedules created before the release keep working by name, which is why the same pipeline configuration can work in one workspace and fail in another. To fix it:
  1. Open the schedule in Bolt and click the schedule name on the schedule details screen. The slug is shown there.
  2. Replace the display name in your CI variable or script (for example PARADIME_SCHEDULE_NAME or PARADIME_SCHEDULE_SLUG) with the slug.
  3. Re-run the pipeline. No other changes are needed.
See Bolt API and the Turbo CI setup guides for current, slug-based pipeline templates.

​
Schedule ’…’ is suspended and cannot be triggered

The schedule exists but is suspended, so API and CI triggers are rejected. Open the schedule in Bolt and resume it, then trigger the run again.

Related topics

Trigger Bolt schedules from DagsterTrigger Bolt schedules from AirflowUnderstanding schedule types and triggersBolt APITriggers