Clear the run history

clear_site_cron_runs

Hides the stored run history of the scheduled jobs on a site.

POST /v1/clear_site_cron_runsScopeconfig:writeDestructive

Pass cronId to clear the history of one job, or leave it out to clear the history of every job on the site. Cleared runs stop appearing in listings but are only erased by the 30 day retention. It reports how many runs it cleared.

The jobs themselves and their schedules are untouched and keep firing. It needs the Delete projects permission in the workspace, the same one the danger zone of the Crons tab asks for. See Scheduled jobs.

Request

Call it with a POST to https://api.modulify.ai/v1/clear_site_cron_runs, sending the inputs below as a JSON object. The token needs the config:write scope.

This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.

curl -X POST https://api.modulify.ai/v1/clear_site_cron_runs \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID"}'

Over MCP, the same method is the clear_site_cron_runs tool.

Inputs

Input	Type	Required	Description
`projectId`	string	Yes	The site id.
`cronId`	string	No	Clear only this job. Leave it out to clear the history of every job on the site.

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.