---
title: "Trigger an existing recurring cron job immediately, without waiting for its own schedule"
method: POST
path: "/projects/{projectId}/cron/{cronJobId}/run"
tags: ["Automation"]
---

# Trigger an existing recurring cron job immediately, without waiting for its own schedule

`POST /projects/{projectId}/cron/{cronJobId}/run`

## Request

- Base URL: `https://hostingsurge.com/api/v1`
- URL: `https://hostingsurge.com/api/v1/projects/{projectId}/cron/{cronJobId}/run`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `__Host-hs_session`

## Path parameters

- `projectId` string, uuid, required
- `cronJobId` string, uuid, required

## Response `200`

Recent executions after triggering

- object
  - `items` object[], required
    - `id` string, required
    - `status` 'success' | 'failed' | 'running', required
    - `message` string, required
    - `durationMs` integer, nullable, required
    - `startedAt` string, nullable, required: ISO-8601 timestamp

## Other responses

- `400`: Invalid request (code invalid_request)
- `401`: Missing or invalid session/token (code unauthorized)
- `403`: Authenticated but not permitted (code forbidden)
- `404`: Not found or not visible to the caller (code not_found)
- `409`: Conflicting state (code conflict)
- `429`: Too many requests (code rate_limited); see Retry-After
- `503`: Hosting engine unavailable (code provider_unavailable)

---

[API](https://skmtc.dev/hostingsurge/apis/hostingsurge-platform-api.md) · [All operations](https://skmtc.dev/hostingsurge/apis/hostingsurge-platform-api/llms.txt) · [OpenAPI document](https://skmtc.dev/hostingsurge/apis/hostingsurge-platform-api/revisions/4d08337cdff1?raw)