overlane task events | Overlane Docs

Lists the project’s domain events in order (task claimed, checkpointed, submitted and so on), starting after a sequence number. Use –after with the last sequence you saw to read only what is new.

Usage

overlane task events [--after SEQUENCE] [--limit N]

Flags

Flag	Type	Required	Default	Description
`--after`	string	no		Only events after this sequence number (default 0)
`--limit`	string	no		How many events to read

Examples

overlane task events
overlane task events --after 120 --limit 50 --json

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: yes.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema task events.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "object",
  "properties": {
    "events": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "sequence": {
            "type": "number"
          },
          "type": {
            "type": "string"
          },
          "occurredAt": {
            "type": "string"
          }
        },
        "required": [
          "sequence",
          "type",
          "occurredAt"
        ],
        "additionalProperties": {}
      }
    }
  },
  "required": [
    "events"
  ],
  "additionalProperties": {}
}

See exit codes for the status the process returns.