ZEzeropath
Agent

Update an agent schedule

Update a recurring assistant schedule. Agent cron schedules run prompts on a recurring time cadence. Use them for polling-style checks, time-window summaries, timeout-rate monitoring, and requests phrased as "every N hours/days" or "on a schedule". For example, create a cron schedule to monitor PR scan timeout rates; do not create a LONG_RUNNING_SCAN event trigger for that recurring workflow. Requires agent management permission. Repository and tag scope are revalidated before changes are saved.

post/api/v2/agent/updateCronSchedule

Request

  • Base URL
    https://zeropath.com
  • Auth
    API key in header X-ZeroPath-API-Token-Id and API key in header X-ZeroPath-API-Token-Secret

Request body

organizationIdstring

Organization ID (injected by MCP server)

scheduleIdstring uuid required

Schedule ID from agent.listCronSchedules.

cronExpressionstring

Standard 5-field cron expression evaluated in UTC. Agent cron schedules run prompts on a recurring time cadence. Use them for polling-style checks, time-window summaries, timeout-rate monitoring, and requests phrased as "every N hours/days" or "on a schedule". For example, create a cron schedule to monitor PR scan timeout rates; do not create a LONG_RUNNING_SCAN event trigger for that recurring workflow.

promptstring
enabledboolean
trustedboolean

Saved Trusted setting. Repository- and tag-scoped jobs always use restricted execution.

modelStrength'LOW' | 'HIGH'
repositoryIdsstring[]

Replace explicit repository selection. To switch to organization-wide scope, explicitly send both repositoryIds: [] and tagIds: [].

tagIdsstring[]

Replace selected tags. Omitting a selection preserves it; clearing one selection alone preserves SELECTED mode.

Response

Schedule updated

Changes

No recorded changes to this operation across all 1 revision of this API.