Skip to content

factory runtime failure: lifecycle triage triage_endpoint_unavailable #54

Closed as not planned

Description

@mikeroysoft-agent

Fingerprint: 8bb659028b22

factory watch observed a runtime failure of the factory itself from local evidence: signal lifecycle, stage triage, 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":"3b8f5e29-9bc0-47ad-9bf3-0f0818d924fe","parent_execution_id":null,"ticket":null,"attempt":null,"review_round":null,"stage":"triage","event":"lifecycle","schema_version":1,"event_id":"a4ca1e4f-86b5-48ab-89e5-62554baf0acd","kind":"exit","at":"2026-10-03T23:20:29.320689Z","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":[],"sequence":8}

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, and factory watch --dry-run no longer reports fingerprint 8bb659028b22.

Activity

  1. mikeroysoft-agent commented on Oct 17, 2026

    @mikeroysoft-agent
    CollaboratorAuthor

    Triage: This issue is a self-referential runtime failure of the factory's own infrastructure: the triage stage exited with mechanism_failure because the triage_endpoint_unavailable. The root cause is that the endpoint the factory depends on for triage is down, which is an operational/infrastructure availability problem rather than a code defect in this repository. Resolving it requires restoring or reconfiguring the triage endpoint service, which lies beyond the code in this repo and needs human authorization and operational intervention.

  2. added 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 workingready-for-humanRequires human implementation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions