GitHub

job.started

A background job or script began: a sync, a backup, a migration

Profile

Logs

Written with

log()

Level

info
View as Markdown

Job intents

Example

TS
log('job.started', 'Redirect sync started', { site: 'main' });
Writes
TS
{
  "intent": "job.started",
  "level": "info",
  "alert": false,
  "message": "Redirect sync started",
  "data": {
    "site": "main"
  },
  "time": "2026-10-09T12:00:00.000Z"
}

Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

  • If it is

    Use

  • A background job or script began: a sync, a backup, a migration

    job.started this page

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add logs puts in your registry. Change levels through the level.* intents, and point log() at your logger.

The entry prongs add logs writes into your registry. Change the level through its level.* ref.

TS
'job.started': {
  kind: 'semantic',
  description: 'A background job or script began: a sync, a backup, a migration',
  refs: ['level.info'],
},