Repository navigation
Report failing setup checks in the weekly stuck-users mail - #1596
Merged
Merged
Conversation
A refused "Check and save" in the guided setup never becomes a tool call, so the weekly report could not see it: a wrong login body in the Éxito adapter blocked a customer for a day without a trace. Section 6 lists, per adapter, the workspaces whose check failed this week and that have not got through since; workspaces whose error may be the adapter's are listed with the error, wrong credentials are counted. The provider message kept in setup_verify_failed grows from 160 to 400 characters, so the provider's own words survive after our hint.
helpcodeai
enabled auto-merge (squash)
November 9, 2026 08:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
A refused "Check and save" in the guided setup (
setup_verify_failed) never becomes a tool call, so the weekly stuck-users report could not see it. On 2026-11-08 a wrong login body in the Éxito adapter (#1584) blocked a customer for a day without a trace in the report; an Odoo probe returning 500 for 8 workspaces was invisible too (#1587).deploy/cloud/stuck-users-report.sh: per adapter, the workspaces whose check failed in the window and that have not got through since (no verifiedsetup_completed, no successful call on that adapter after the first failure), with the failure kinds and statuses. When the error may be the adapter's (bad_request, not_found, upstream_error, error…) the top 3 error texts and the workspaces are listed, also on free-mail addresses; customer-side kinds (auth_failed, rate_limited, invalid_input, unreachable) are counted. Etsy stays in section 5. The summary/subject gains "N workspaces stuck at a setup check (M possibly the adapter)".scrubProviderMessagekeeps 400 characters instead of 160, so the provider's own words survive after our hint (the OdooInvalid field 'customer_rank'was cut off).Dry run on Cloud (read-only,
--print): 82 of 175 workspaces with a failed check this week not through, 37 with an error that may be ours; it lists the Éxito 400, the Odoo 500, YouTube Data's 400s and others.Cloud and self-hosted
The report runs on the Cloud droplet only (systemd timer). The longer provider message applies to both modes.
Tests
bash deploy/cloud/stuck-users-report.test.sh→ all checks passed (new section 6 checks: adapter-side failure listed with scrubbed text on free mail, credential failure counted not listed, fixed setups and Etsy not listed, totals in the summary).packages/backend:npx jest src/audit/product-event --maxWorkers=4→ passed;npx tsc --noEmit -p tsconfig.json→ clean; eslint on the changed files → clean.