iiRecord
Agentic AI Atlas · Schedule Trigger
definition:trigger-schedulea5c.ai
II.
Definition JSON

definition:trigger-schedule

Structured · live

Schedule Trigger json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · domain/cicd/cicd-concepts.yamlCluster · domain
Record JSON
{
  "id": "definition:trigger-schedule",
  "_kind": "Definition",
  "_file": "domain/cicd/cicd-concepts.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "Schedule Trigger",
    "authoredAt": "2026-05-10T00:00:00Z",
    "termId": "term:cicd",
    "text": "A CI trigger that fires on a cron schedule. Defined using standard\ncron expressions (e.g., '0 6 * * 1' for Monday 06:00 UTC). Used for\nnightly builds, weekly security scans, periodic claim verification,\nand freshness checks. Schedule triggers always run against the\ndefault branch. Multiple cron expressions can be defined to support\ndifferent cadences for different job types within the same workflow.\n",
    "status": "canonical"
  },
  "outgoingEdges": [
    {
      "from": "definition:trigger-schedule",
      "to": "term:cicd",
      "kind": "defines"
    },
    {
      "from": "definition:trigger-schedule",
      "to": "domain:devops",
      "kind": "applies_to"
    },
    {
      "from": "definition:trigger-schedule",
      "to": "tool:github-actions",
      "kind": "supports"
    },
    {
      "from": "definition:trigger-schedule",
      "to": "tool:gitlab-ci",
      "kind": "supports"
    },
    {
      "from": "definition:trigger-schedule",
      "to": "tool:jenkins",
      "kind": "supports"
    },
    {
      "from": "definition:trigger-schedule",
      "to": "topic:ci-triggers",
      "kind": "supports"
    }
  ],
  "incomingEdges": []
}