Skip to content

[BLOCKER] RAILWAY_TOKEN_ACC1/ACC2 secrets invalid — writer-env-fix cannot heal writer #156

@gHashTag

Description

@gHashTag

Problem

Cure A (writer-env-fix.yml) failed on run #2 (2026-05-14T05:35Z) because RAILWAY_TOKEN_ACC1 secret is invalid. Error:

##[error]token ACC1 failed sanity check
##[error]Process completed with exit code 3

Backboard GraphQL endpoint https://backboard.railway.com/graphql/v2 returned non-success when queried with this token — meaning Railway has revoked or rotated the token, but the GitHub Actions secret was not updated.

Impact

  • IGLA writer dead 560+ minutes (ssot.bpb_samples stalled since 2026-05-13 20:14Z).
  • Cure A cannot run.
  • All matrix-runner deploys are unreachable through this token path.

Operator action required

  1. Generate fresh team-scoped Railway tokens for ACC1 + ACC2 in https://railway.app/account/tokens.
  2. Update GitHub secrets in gHashTag/trios-railway:
    • RAILWAY_TOKEN_ACC1
    • RAILWAY_TOKEN_ACC2
  3. Re-run writer-env-fix.yml with confirm=PHI.
  4. Verify via SQL probe:
    SELECT COUNT(*) FILTER (WHERE ts > now() - interval '5 minutes')::int AS rows_5m,
           ROUND(EXTRACT(EPOCH FROM (now() - MAX(ts)))/60) AS min_since_last
    FROM ssot.bpb_samples WHERE canon_name LIKE 'IGLA-%';
    Expect rows_5m > 0 within 5 min.

Evidence

Failed run: https://github.com/gHashTag/trios-railway/actions/runs/25843795652
Throne meta: gHashTag/trios#264

Anchor: phi^2 + phi^-2 = 3

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockerauto-created by gardener v2.7

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions