job
El dominio job tiene 11 acciones. En la superficie meta se alcanzan todas a través de arcane_job; en la individual, cada una es una herramienta propia; en la dinámica se ejecutan con arcane_execute_action y el ID canónico.
Resumen
Sección titulada «Resumen»| Acción | Título | Tipo |
|---|---|---|
job.ack_run | Acknowledge remote run completion | escritura |
job.cancel_run | Cancel pending job run | escritura |
job.get_run | Get job run | lectura |
job.list | List all background jobs | lectura |
job.list_runs | List job runs | lectura |
job.resolve_run | Resolve legacy job run | escritura |
job.restart_worker | Restart continuous job worker | escritura |
job.retry_run | Retry job run | escritura |
job.run | Run a job now | escritura |
job.schedules_get | Get job schedules | lectura |
job.schedules_update | Update job schedules | escritura |
Acciones
Sección titulada «Acciones»job.ack_run
Sección titulada «job.ack_run»Acknowledge remote run completion
- Tipo: escritura
- Parámetros obligatorios:
jobId,runId - Meta-herramienta:
arcane_jobcon"action": "ack_run" - Herramienta individual:
arcane_job_ack_run - Ruta de Arcane:
POST /api/environments/{id}/jobs/{jobId}/runs/{runId}/ack - ID de operación:
ack-job-run - Desde: Arcane v2.11.0
- Uso: Marks a finished run’s remote delivery as settled (remoteSettled true) so retention can compact its history. It does not change the run’s status. The run must be terminal (succeeded, partial, skipped, failed or canceled). runId from job.run or job.list_runs.
- Acciones relacionadas:
job.get_run,job.list_runs,job.retry_run
job.cancel_run
Sección titulada «job.cancel_run»Cancel pending job run
- Tipo: escritura
- Parámetros obligatorios:
jobId,runId - Meta-herramienta:
arcane_jobcon"action": "cancel_run" - Herramienta individual:
arcane_job_cancel_run - Ruta de Arcane:
POST /api/environments/{id}/jobs/{jobId}/runs/{runId}/cancel - ID de operación:
cancel-job-run - Desde: Arcane v2.11.0
- Uso: Cancels a run only while it is queued and never attempted or delivered (otherwise ‘only unstarted pending runs can be canceled’). It cannot stop a running job. runId from job.run or job.list_runs. In practice only a run queued behind a still-running run of the same job is catchable. The result is the run with status canceled.
- Acciones relacionadas:
job.list_runs,job.get_run,job.run
job.get_run
Sección titulada «job.get_run»Get job run
- Tipo: lectura
- Parámetros obligatorios:
jobId,runId - Meta-herramienta:
arcane_jobcon"action": "get_run" - Herramienta individual:
arcane_job_get_run - Ruta de Arcane:
GET /api/environments/{id}/jobs/{jobId}/runs/{runId} - ID de operación:
get-job-run - Desde: Arcane v2.11.0
- Uso: Reads one run: status (queued, waiting, running, retrying, succeeded, partial, skipped, failed, canceled, or legacy needs_attention), attemptCount, attempts, outcome, activityId (for activity.get, set on manual and other user-visible runs), timestamps and remote delivery flags. runId comes from job.run or job.list_runs. Poll this after job.run until the status is terminal.
- Acciones relacionadas:
job.run,job.list_runs,job.retry_run,job.ack_run,activity.get
job.list
Sección titulada «job.list»List all background jobs
Get status, schedule, and metadata for all background jobs
- Tipo: lectura
- Parámetros obligatorios: ninguno
- Meta-herramienta:
arcane_jobcon"action": "list" - Herramienta individual:
arcane_job_list - Ruta de Arcane:
GET /api/environments/{id}/jobs - ID de operación:
list-jobs - Uso: Start here: lists every background job of the environment with its id (the jobId of the other job actions), schedule, nextRun, enabled, canRunManually, isContinuous, prerequisites, currentRun and lastRun. For a remote environment the agent’s catalog is returned (isAgent true). Requires the jobs:manage permission.
- Acciones relacionadas:
job.run,job.list_runs,job.schedules_get,job.restart_worker
job.list_runs
Sección titulada «job.list_runs»List job runs
- Tipo: lectura
- Parámetros obligatorios:
jobId - Meta-herramienta:
arcane_jobcon"action": "list_runs" - Herramienta individual:
arcane_job_list_runs - Ruta de Arcane:
GET /api/environments/{id}/jobs/{jobId}/runs - ID de operación:
list-job-runs - Desde: Arcane v2.11.0
- Uso: Paginated run history of one job (jobId from job.list): page (default 1) and limit (default 20, max 100). The result has runs, total, page and limit. For a remote environment it merges the agent’s history with the manager’s delivery records. Use it to find a runId for job.get_run, job.retry_run or job.ack_run.
- Acciones relacionadas:
job.list,job.get_run,job.retry_run,job.ack_run
job.resolve_run
Sección titulada «job.resolve_run»Resolve legacy job run
Deprecated compatibility endpoint for mixed-version upgrades. Removed in v3.
- Tipo: escritura
- Parámetros obligatorios:
jobId,runId - Meta-herramienta:
arcane_jobcon"action": "resolve_run" - Herramienta individual:
arcane_job_resolve_run - Ruta de Arcane:
POST /api/environments/{id}/jobs/{jobId}/runs/{runId}/resolve - ID de operación:
resolve-job-run - Desde: Arcane v2.11.0
- Uso: Deprecated (removed in Arcane v3): marks a needs_attention run as reviewed by setting it canceled with a resolution. Any other status is refused with ‘only runs needing attention can be resolved’. Arcane (v2.16.1 to v2.17.2) records such outcomes as failed, so only runs of agents older than v2.16 can still be resolved. Otherwise use job.retry_run or job.run. Leave resolvedBy empty: only the manager-to-agent transport may set it.
- Acciones relacionadas:
job.get_run,job.retry_run,job.ack_run
job.restart_worker
Sección titulada «job.restart_worker»Restart continuous job worker
- Tipo: escritura
- Parámetros obligatorios:
jobId - Meta-herramienta:
arcane_jobcon"action": "restart_worker" - Herramienta individual:
arcane_job_restart_worker - Ruta de Arcane:
POST /api/environments/{id}/jobs/{jobId}/restart - ID de operación:
restart-job-worker - Desde: Arcane v2.11.0
- Uso: Restarts the worker of a continuous job (isContinuous true in job.list, e.g. image-polling). Other jobs fail with ‘watcher not found’. It does not queue a run: use job.run for scheduled jobs. Remote environments forward the request to the agent.
- Acciones relacionadas:
job.list,job.run
job.retry_run
Sección titulada «job.retry_run»Retry job run
- Tipo: escritura
- Parámetros obligatorios:
jobId,runId - Meta-herramienta:
arcane_jobcon"action": "retry_run" - Herramienta individual:
arcane_job_retry_run - Ruta de Arcane:
POST /api/environments/{id}/jobs/{jobId}/runs/{runId}/retry - ID de operación:
retry-job-run - Desde: Arcane v2.11.0
- Uso: Requeues an existing run under the same runId, keeping its target progress. Only failed, partial or needs_attention runs are eligible (others fail with ‘run is not eligible for retry’), and on the local environment the job must still be enabled with its prerequisites met. Remote work whose outcome is not yet confirmed is refused (‘remote outcome must be confirmed before retry’). Poll job.get_run afterwards: attemptCount grows. To start a fresh run use job.run instead.
- Acciones relacionadas:
job.list_runs,job.get_run,job.run
job.run
Sección titulada «job.run»Run a job now
Manually trigger a background job to run immediately
- Tipo: escritura
- Parámetros obligatorios:
jobId - Meta-herramienta:
arcane_jobcon"action": "run" - Herramienta individual:
arcane_job_run - Ruta de Arcane:
POST /api/environments/{id}/jobs/{jobId}/run - ID de operación:
run-job - Uso: Queues a run of jobId (from job.list, and the job must be enabled, have canRunManually true and its prerequisites met) and returns 202 with runId and status. The job runs in the background. runId is optional: Arcane assigns a UUID when it is omitted, and passing your own UUID (as runId or idempotencyKey, which must agree) makes a repeated call return the same run instead of queuing another. Poll job.get_run with jobId and the returned runId until status is succeeded, failed, partial, skipped or canceled.
- Acciones relacionadas:
job.list,job.get_run,job.list_runs,job.cancel_run
job.schedules_get
Sección titulada «job.schedules_get»Get job schedules
Get configured cron schedules for background jobs
- Tipo: lectura
- Parámetros obligatorios: ninguno
- Meta-herramienta:
arcane_jobcon"action": "schedules_get" - Herramienta individual:
arcane_job_schedules_get - Ruta de Arcane:
GET /api/environments/{id}/job-schedules - ID de operación:
get-job-schedules - Uso: Returns the cron expressions of the configurable job intervals (environmentHealthInterval, eventCleanupInterval, pollingInterval, scheduledPruneInterval, autoUpdateInterval, vulnerabilityScanInterval and others). Read it before job.schedules_update. job.list shows each job’s effective schedule and nextRun.
- Acciones relacionadas:
job.schedules_update,job.list
job.schedules_update
Sección titulada «job.schedules_update»Update job schedules
Update background job cron schedules and reschedule running jobs
- Tipo: escritura
- Parámetros obligatorios: ninguno
- Meta-herramienta:
arcane_jobcon"action": "schedules_update" - Herramienta individual:
arcane_job_schedules_update - Ruta de Arcane:
PUT /api/environments/{id}/job-schedules - ID de operación:
update-job-schedules - Uso: Changes only the interval fields you pass (omit the others). Each value is a six-field cron expression with seconds (e.g. ‘0 30 */6 * * *’) or a descriptor such as ‘@every 5m’, and an invalid one rejects the whole request. Affected jobs are rescheduled immediately and the full schedule config is returned. Refused when Arcane’s UI configuration is disabled.
- Acciones relacionadas:
job.schedules_get,job.list