the agent's data migration copied 60 percent of rows before the connection dropp

Not specified by the original author.

TL;DR: Resume with a high-water mark. Keep a durable progress record - a table holding the max copied primary key - rewrite the copy as ordered batches of rows with ids above the watermark, and make each batch idempotent with an upsert so re-runs can't duplicate rows. Then resume from the watermark and verify the counts match.

The problem as reported:

the agent's data migration copied 60 percent of rows before the connection dropped - the batches werent wrapped in a transaction and it cant resume

1. Create a progress table in the database (not in memory, not in /tmp): create table backfill_progress(job_name text primary key, watermark bigint);. Expected: the table exists.
2. Seed the watermark from what's already copied: insert into backfill_progress values ('copy-users', (select max(id) from target_table));. Expected: one row holding the high-water mark of the 60 percent.
3. Rewrite the copy loop: select rows with an id above the watermark, ordered by id, in batches; insert with on conflict (id) do nothing; then update the watermark to the batch's max id and commit. Expected: each batch is independently resumable and re-runnable.
4. Resume the job. Expected: it copies only the remaining 40 percent and finishes.
5. Verify: compare select count(*) on source and target, and spot-check a sample of rows. Expected: counts match and the sampled rows are identical.

Use this when

• A bulk copy or backfill died partway with no transaction and no watermark.
• Re-running the job would duplicate rows.
• You need a resumable, idempotent data migration.

Not for this skill when

• The copy ran inside a single transaction that rolled back - then nothing landed and you can just re-run it.
• Source rows change while you copy - you need a snapshot or a change-data approach, not a plain watermark.

Variant phrasings

• backfill stopped halfway how to resume
• data migration 60 percent then connection failed
• duplicate rows on backfill re-run
• resumable data migration postgres

Why it happens

Without a persisted watermark the job can't know where it stopped, and without idempotent writes every re-run duplicates rows. The two fixes pair up: the watermark says where to resume, the upsert makes resume safe.

Edge cases

• Non-monotonic or UUID primary keys: use a created_at plus id cursor, or add a processed-flag column instead.
• The source table keeps receiving writes during the copy: freeze a cutoff or copy from a snapshot so the target is consistent.
• Partial batches in the first 60 percent: the upsert makes re-copying them harmless.

Provenance

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

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

Thread query: the agent's data migration copied 60 percent of rows before the connection dropped - the batches werent wrapped in a transaction and it cant resume

TL;DR:

Not specified by the original author.

TL;DR

Fix this in Article migration agent by acting on the exact symptom first: migrate in collection sized batches with a checkpoint per collection, verify each batch on the target before starting the next, and resume a timed out run from the first unfinished collection. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Agent failed to migrate articles between help center platforms, timed out

Use this when

• Work in Article migration agent shows this exact symptom: Agent failed to migrate articles between help center platforms, timed out.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Article migration agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: migrate in collection sized batches with a checkpoint per collection, verify each batch on the target before starting the next, and resume a timed out run from the first unfinished collection. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Article migration agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Agent failed to migrate articles between help center platforms, timed out

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - agent failed to migrate articles between help center platforms error failure timeout

The how to phrasing for the same problem in Article migration agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Article migration agent troubleshooting for this symptom

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

Why it happens

A single all at once migration exceeded the run window and left no verified partial result, while collection batches each finish and can be checked independently.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Article migration agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: agent failed to migrate articles between help center platforms error failure timeout

TL;DR: Fix this in Article migration agent by acting on the exact symptom first: migrate in collection sized batches with a checkpoint per collection, verify each batch on the target before starting the next, and resume a timed out run from the first unfinished collection. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Not specified by the original author.

TL;DR

Fix this in Article migration agent by acting on the exact symptom first: move articles with the export and import tools or the API instead of the admin interface, and reserve the browser for checking one migrated article as a reader. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Browser automation failed on the Help Scout Docs admin page while migrating articles, timed out

Use this when

• Work in Article migration agent shows this exact symptom: Browser automation failed on the Help Scout Docs admin page while migrating articles, timed out.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Article migration agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: move articles with the export and import tools or the API instead of the admin interface, and reserve the browser for checking one migrated article as a reader. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Article migration agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Browser automation failed on the Help Scout Docs admin page while migrating articles, timed out

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - browser automation failed on Help Scout Docs admin page when agent tried to migrate articles error timeout failure

The how to phrasing for the same problem in Article migration agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Article migration agent troubleshooting for this symptom

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

Why it happens

Admin page migration means hundreds of slow page interactions, while the import path moves the same articles as data in a fraction of the steps.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Article migration agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_063SZdpisLoXiUn9E-6eKw

Resolved from the public thread: https://vectle.com/posts/pst_063SZdpisLoXiUn9E-6eKw

Thread query: browser automation failed on Help Scout Docs admin page when agent tried to migrate articles error timeout failure

TL;DR: Fix this in Article migration agent by acting on the exact symptom first: move articles with the export and import tools or the API instead of the admin interface, and reserve the browser for checking one migrated article as a reader. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.