Skip to content

factory runtime failure: lifecycle triage-ticket triage_endpoint_unavailable #53

Closed as not planned

Description

@mikeroysoft-agent

Fingerprint: a60ef4d592b6

factory watch observed a runtime failure of the factory itself from local evidence: signal lifecycle, stage triage-ticket, triage_endpoint_unavailable. Filed automatically; no human has looked at it yet.

Evidence

Journal rows (1 newest)

{"dispatcher_run_id":null,"root_execution_id":"3b8f5e29-9bc0-47ad-9bf3-0f0818d924fe","execution_id":"c2e25a8a-3334-4bc6-ae9f-64f4989f33a5","parent_execution_id":"3b8f5e29-9bc0-47ad-9bf3-0f0818d924fe","ticket":46,"attempt":null,"review_round":null,"stage":"triage-ticket","event":"lifecycle","schema_version":1,"event_id":"2210882b-526a-4a2a-a1a4-05f2ef0d88e0","kind":"exit","at":"2026-10-03T23:20:29.315565Z","outcome":"mechanism_failure","reason":"triage_endpoint_unavailable","process":{"pid":1227215,"boot_id":"8799e8c2-3387-4aa7-a525-c71ce4d444c7","start_ticks":35383548,"pid_namespace":"pid:[4026531836]","uid":1000,"state":"R","ppid":1567},"locks":[{"path":"/tmp/factory.lock","device":58,"inode":1735},{"path":"/tmp/factory.lock","device":58,"inode":1735}],"sequence":7}

Reproduce

zcat -f .factory/events.jsonl* | grep -F '"reason":"triage_endpoint_unavailable"'
factory watch --dry-run

Expected behavior

The factory pass completes without triage_endpoint_unavailable at stage triage-ticket, and factory watch --dry-run no longer reports fingerprint a60ef4d592b6.

Activity

  1. mikeroysoft-agent commented on Oct 17, 2026

    @mikeroysoft-agent
    CollaboratorAuthor

    Triage: This is a self-referential infrastructure failure: the factory's own triage stage failed with triage_endpoint_unavailable, meaning the endpoint the factory calls to perform triage was not reachable. The evidence only records the symptom (a mechanism_failure exit at stage triage-ticket) and does not identify the root cause. It could be a transient network outage, a missing/invalid credential, a misconfiguration, or an external service being down. Until the root cause is known, it is impossible to tell whether this is a code fix, a config/credential fix, or an environmental condition that will resolve on its own, so the reporter must be asked for the specifics before any action can be taken.

    Question: What is the triage endpoint that the factory calls at stage triage-ticket, and why was it unavailable (network outage, missing/invalid credential, misconfiguration, or external service down)? Is this a transient failure that recovers on retry, or a persistent condition?

  2. added
    needs-infoWaiting on reporter for more information
    and removed
    needs-triageMaintainer needs to evaluate this issue
    on Oct 17, 2026
  3. mikeroySoft commented on Oct 19, 2026

    @mikeroySoft
    Owner

    Duplicate of mikeroySoft/factory#261 / ROCm#262 (host condition; no longer filed since ROCm#281). Stopping watch from filing engine bugs here is tracked in mikeroySoft/factory#311. Engine bugs are tracked in mikeroySoft/factory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds-infoWaiting on reporter for more information

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions