Daily verb run RED 2026-09-28: 5 failing verb(s)

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 1mo ago ·closed by John Lauer

Automated daily verb run went red (2026-09-28, exit 1). Scorecard tail:

  fusion_plan_route#guard                    PASS 
  fusion_schematic#guard                     PASS 
  fusion_schematic#missing                   PASS 
  fusion_make_showcase_project#guard         PASS 
  fusion_eagle_import_status#guard           PASS 
  fusion_show_attributes#guard               PASS 
  focus_invariance                           PASS
cleanup: Fusion was already running before the run - leaving it (user's session).

Section coverage (John's product map, 2026-08-14):
  gui-driving                            17 pass / 0 fail (21 manual, 0 skip)  green
  cad-3d-bom                             15 pass / 0 fail (7 manual, 0 skip)  green
  mcp-server                             1 pass / 0 fail (1 manual, 0 skip)  green
  python-addin                           6 pass / 0 fail (1 manual, 0 skip)  green
  aps                                    5 pass / 4 fail (13 manual, 0 skip)  RED
  auth-tokens                            2 pass / 1 fail (5 manual, 0 skip)  RED
  exports                                0 pass / 0 fail (1 manual, 0 skip)  untested-this-tier
  bridge-lifecycle                       12 pass / 0 fail (15 manual, 0 skip)  green

62 PASS, 5 FAIL (68 manual-tier, 0 skipped) -> /home/adom/project/adom-desktop-fusion-bridge/tests/reports/verb-test-2026-09-28_1149.json
  FAIL: fusion_aps_search - expected success, got error=Not signed in to APS. code=aps_not_signed_in; expected >0 results
  FAIL: fusion_aps_recent - expected success, got error=Not signed in to APS. code=aps_not_signed_in; expected >0 results
  FAIL: fusion_aps_browse - expected success, got error=Not signed in to APS. code=aps_not_signed_in; missing field 'hubs'
  FAIL: fusion_aps_file_info - expected success, got error=Not signed in to APS. code=aps_not_signed_in; missing field 'versionCount'
  FAIL: fusion_aps_get - expected success, got error= code=None

Full log: tests/reports/daily-cron-2026-09-28.log on the dev container. Versions at run time are in the readiness line of the log. Triage per dev-skills/fusion-verb-tests: re-run the failing verbs with --only first, a startup race or relay flake re-passes; a repeat failure is the real finding.

1 Reply

John Lauer · 1mo ago

Root cause found and fixed in 1.11.8, now public.

All five failures in each of these runs (2026-09-24 through 09-28, #100-#104) are one thing: ConfRoomROG's cloud-search (APS) sign-in died. The access token expired on 09-24 and the automatic refresh failed from then on.

Why the refresh failed. Cloud search refreshed the token from up to 12 parallel search workers at once, and the janitor and status calls could refresh from other processes at the same moment, all sending the SAME single-use refresh token. Autodesk rotates refresh tokens and can revoke the whole token family when one is replayed, after which every refresh fails until someone signs in again.

Fix (1.11.8): one refresher at a time across threads and processes (a lock file plus an in-process mutex); once the lock is held the tokens are re-read, so a refresh another worker just finished is reused instead of repeated; tokens.json is written atomically; and Autodesk's refusal is kept in last_refresh_error.json so the next failure explains itself.

Recovery: ConfRoomROG was signed back in to cloud search as [email protected] (Google, then Allow). The full suite on the signed 1.11.8 there: 67 pass, 0 fail (report verb-test-2026-09-29_0311.json).

Closing all five.

John Lauer closed this · 1mo ago