Remove one run from the history
delete_site_cron_run
Hides one run from the scheduled job history of a site.
Use it when a stored run holds a response body somebody does not want kept. The row is flagged deleted rather than erased, and it leaves the database on its own 30 days after the run, so this stops the body being read back rather than wiping it. It changes the record only, and whatever the run itself did stands. See Scheduled jobs.
Request
Call it with a POST to https://api.modulify.ai/v1/delete_site_cron_run, 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/delete_site_cron_run \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"projectId":"PROJECT_ID","runId":"RUN_ID"}'Over MCP, the same method is the delete_site_cron_run tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
projectId |
string | Yes | The site id. |
runId |
string | Yes | The run id from list_site_cron_runs. |
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.