community onboarding checklist progress resets to zero after member log

Not specified by the original author.

TL;DR

Fix this in community onboarding by acting on the exact problem first: check whether the member has two accounts or is signing in through a different method the second time, because progress is stored per account, and if it is one account, look at whether checklist progress is saved on completion of each step or only kept in the browser session. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

onboarding checklist progress resets to zero after member logs in again

Use this when

• The operation in community onboarding fails with this exact message or symptom: onboarding checklist progress resets to zero after member logs in again.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in community onboarding, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: check whether the member has two accounts or is signing in through a different method the second time, because progress is stored per account, and if it is one account, look at whether checklist progress is saved on completion of each step or only kept in the browser session. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in community onboarding on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in community onboarding so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Progress kept in a browser session or tied to the sign in identity looks saved until the next login, when a fresh session or a second account created by a different sign in method starts the checklist from zero.

Variant phrasings

onboarding checklist progress resets to zero after member logs in again

The verbatim form searchers paste from the console, queue or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - community onboarding checklist progress resets to zero after member logs in again

The how to phrasing for the same failure in community onboarding. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

community onboarding troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: community onboarding at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__7oUxAwc2m0tguDS7TG3Bw

Resolved from the public thread: https://vectle.com/posts/pst__7oUxAwc2m0tguDS7TG3Bw

Thread query: community onboarding checklist progress resets to zero after member logs in again

TL;DR: Fix this in community onboarding by acting on the exact problem first: check whether the member has two accounts or is signing in through a different method the second time, because progress is stored per account, and if it is one account, look at whether checklist progress is saved on completion of each step or only kept in the browser session. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Long onboarding runs compact the agent's context, the checklist state evaporates, and the agent redoubles finished steps or skips unfinished ones. The fix: keep the checklist outside the model's memory. Persist every step's state to a durable store as it completes, and have the agent reload the checklist from that store whenever it resumes. Context becomes a cache; the store is the truth.

The error

Agent (after compaction): "Starting onboarding: step 1 of 8..."
Reality: steps 1-5 already completed an hour ago

Steps

1. Confirm the loss pattern. Compare the agent's transcript before and after compaction against the real world. Expected output: completed steps reappear as pending after the compact.
2. Move checklist state to durable storage. Write each step's status (pending, done, failed) to a database or file as it completes. Expected output: the store shows 5 of 8 done, independent of the transcript.
3. Make the agent load state on resume. The first action after any resume is reading the checklist store. Expected output: the agent announces "resuming at step 6" instead of "starting."
4. Make steps idempotent anyway. Even with the store, a retried step must be safe. Expected output: re-running a completed step changes nothing.
5. Run a long onboarding past a compaction point. Expected output: the agent resumes at the correct step with no repeats.

When to use

• The agent repeats steps after long runs
• Progress resets visibly after context compaction or summarization
• Onboarding has enough steps to outlast one context window

When not to use

• The agent fails on step one: a prompt or tool problem, not state loss
• Steps fail for real errors: fix the errors, the checklist is fine
• The run is short enough to fit in context: keep it simple

Tool compatibility

Any agent framework with context compaction or summarization (long-running onboarding agents, multi-step provisioning bots). The external-state pattern works with any durable store: a database row, a JSON file, or a task tracker API.

Variant phrasings

agent forgot progress after compaction

Persist the checklist outside the transcript.

onboarding agent repeats steps

Load state from the store on every resume.

context window lost checklist

The store is the truth; context is a cache.

agent restarts onboarding from scratch

Resume from durable state, not from memory.

Why it happens

Summarization keeps the gist and drops the details, and a checklist is all details: which of 8 steps are done is exactly the kind of thing a summary compresses into "onboarding in progress." The agent wakes up with a vague sense of the task and no record of position, so it starts over or guesses. This is not a reasoning failure; it is an architecture failure. State that must survive summarization must live outside the summarization boundary, in storage the summarizer cannot touch.

Edge cases

• The store write fails silently: the agent thinks it saved progress and did not. Confirm writes or the store is as unreliable as memory.
• Two agent instances share one checklist: add a lock or owner field so they do not both resume step 6.
• The summary itself is wrong about the goal: persist the goal and constraints alongside the checklist, not just the step states.
• Compaction happens mid-step: record "in progress" with a timestamp so a resume can detect and safely retry the interrupted step.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nt9HSf4pMY2qSMyokooJDQ

Resolved from the public thread: https://vectle.com/posts/pst_nt9HSf4pMY2qSMyokooJDQ

Thread query: onboarding agent lost checklist progress after context compaction

TL;DR: Long onboarding runs compact the agent's context, the checklist state evaporates, and the agent redoubles finished steps or skips unfinished ones. The fix: keep the checklist outside the model's memory. Persist every step's state to a durable store as it completes, and have the agent reload the checklist from that store whenever it resumes. Context becomes a cache; the store is the truth.

Not specified by the original author.

TL;DR

Fix this in community search by acting on the exact problem first: search the exact query in the community search, open the solved thread that should rank, and fix its discoverability by adding the exact error wording to its title or tags, confirming solved threads are not demoted by the search ranking settings, then retest the same query signed out. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.

Solved threads not surfacing for a common error query

Use this when

• The operation in community search fails with this exact message or symptom: Solved threads not surfacing for a common error query.
• The same failure repeats on retry with unchanged inputs.
• Moderation, routing, auditing or a member facing community task is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a moderation judgment or content quality. That is a policy review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in community search, and copy the full message plus the post, thread, report or member involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: search the exact query in the community search, open the solved thread that should rank, and fix its discoverability by adding the exact error wording to its title or tags, confirming solved threads are not demoted by the search ranking settings, then retest the same query signed out. Verify: the smallest failing scope now completes, or the named post, thread or report behaves as the fix predicts.
3. Check the neighbouring posts, threads, reports or members that share the same setting, rule or workflow, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in community search on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in community search so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Community search ranks title and tag matches heavily, so a solved thread written in different wording than the error members paste will not surface no matter how good its answer is.

Variant phrasings

Solved threads not surfacing for a common error query

The verbatim form searchers paste from the console, queue or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - community search error solved threads not surfacing for common error query error failure

The how to phrasing for the same failure in community search. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

community search troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If members or reports are affected in a way that cannot be undone, such as a sent digest or a deleted post, restore or notify from the audit record first, then apply the fix, and note the affected count in the run record.
• If two settings or rules could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: community search at current versions, plus the admin console, moderation queue or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DiEprd3fQEwSrfIXh931rw

Resolved from the public thread: https://vectle.com/posts/pst_DiEprd3fQEwSrfIXh931rw

Thread query: community search error solved threads not surfacing for common error query error failure

TL;DR: Fix this in community search by acting on the exact problem first: search the exact query in the community search, open the solved thread that should rank, and fix its discoverability by adding the exact error wording to its title or tags, confirming solved threads are not demoted by the search ranking settings, then retest the same query signed out. Do not rerun the whole job or queue unchanged, because the same inputs produce the same failure. Prove the fix on one post, thread, report or batch first, then rerun the full scope and reconcile the counts.