Repository navigation
specs/functions: crm-proactive-sweep -- one step per seller after the 502 runs - #4113
Merged
Merged
Conversation
This was referenced Sep 17, 2026
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This was referenced Sep 17, 2026
This was referenced Oct 2, 2026
…01 (999 main @7d48227)
The sweep-per-seller change landed on 999-multibots-telegraf main and the
createFunction call now sits at line 101, not 41. STEPS (resolve-sellers,
sweep-${owner}), RETRIES 0 and concurrency 1 re-read on that revision.
Refs #4112
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-10-02 20:19:40 UTC
Summary
Seal Status
|
Contributor
PR DashboardGenerated at: 2026-10-02 20:21:25 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Owner
Author
|
bee review (not merged) -- head Content is sound:
Blocker: To clear: re-date the NOW entry (or add one dated today) on the branch. |
The NOW sync gate reads the entry date from the filename and accepts only yesterday..tomorrow UTC. The entry was dated 2026-09-17; it is moved to 2026-10-03 with its heading, and a line says it was re-dated for re-review. Refs #4112 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
PR DashboardGenerated at: 2026-10-02 20:54:36 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
gHashTag
added
the
bee-reviewed
Owner
Author
|
Bee review evidence -- #4113 at
|
![t27-bees[bot]](https://avatars.githubusercontent.com/in/5166765?s=60&v=4){kind=small}
This was referenced Oct 6, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #4112
New spec
specs/functions/crm-proactive-sweep.t27for the Inngest cron that had none. Three FAILED runs on 2026-09-16 (15 s / 2m02s / 5m00s) all read "HTTP 502 before the SDK responded" on the self-hosted dashboard: the tick was onestep.run('sweep'), one HTTP request carrying every seller (each up to 170 s). Spec says STEPS =resolve-sellers,sweep-${owner}, RETRIES 0, and NOTE records the finding and what was not verified.crm.docs/now/2026-09-17-the-sweep-gets-one-step-per-seller.md.published_figures.py --checkdrifts 6 figures on master already (test blocks 13218 vs pin 12783); this PR adds no test blocks and does not touch the pin.Code follows in 999-multibots-telegraf branch
sweep-per-seller-steps.