Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
The docs say three identical successful heals of the same locator produce a page-object patch proposal. Ours has healed five times across four nightly runs, same description, same winning selector, and:
sdods proposals list --status pendingcomes back empty. The page object does use heal.locator, so this should be the deterministic path rather than the agent one.
Accepted answer
The counting does not happen during the run, it happens in insights, and insights reads a database rather than the run directories. If your nightly is not ingesting, the heal events are sitting in heal.jsonl where nothing is aggregating them.
sdods run -p portal -e staging -l ui --ingestsdods insights compute -p portalA locator becomes hot when its fragility clears the threshold and it has at least three heals, and hot locators are what the trigger watches. Check sdods insights show -p portal first: if the locator is not in the fragility table at all, the events never reached the database and no amount of waiting will produce a proposal.
Also worth ruling out the boring one: proposals are per project, so sdods proposals list -p <slug> rather than the bare form if you have several in the workspace.
And the scheduler only spawns the command. If nothing is scheduled, nothing computes on its own and insights are as fresh as the last time somebody ran them.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.