raw cell mis-identified as code crashed when agent tried to execute it

Not specified by the original author.

TL;DR

Raw cells hold unformatted text (often LaTeX or notes) that is not python, so executing one's source raises SyntaxError or worse. The agent must check cell.cell_type == 'code' before executing anything, and treat raw and markdown cells as non-executable by construction. This is a one-line filter that prevents a whole class of crashes.

raw cell mis-identified as code crashed when agent tried to execute it

Use this when

• An agent executes a raw cell's content as python and crashes.
• The agent iterates cells without checking cell_type.
• Notebooks contain raw cells (nbconvert targets, LaTeX).

Not for this skill when

• A code cell crashes. That is a code bug.
• A human runs the raw cell. The UI does not execute raw cells either.

Steps

1. Add the filter: only execute cells where cell.cell_type == 'code'. Verify: raw and markdown cells are skipped.
2. Audit the agent's cell loop for other type assumptions. Verify: every branch handles all three cell types.
3. Add a test notebook containing raw cells with python-looking text. Verify: the agent skips them.
4. Log skipped cells at debug level. Verify: the log shows what was skipped and why.
5. Re-run the agent on the failing notebook. Verify: no crash, raw cells untouched.

Variant phrasings

agent execute raw cell crash

Short form. Filter by cell_type.

raw cell as code SyntaxError

The error phrasing. Raw is not python.

cell_type filter agent execution

The fix phrasing. One-line guard.

Compatibility: nbformat 5.x cell types: code, markdown, raw. The filter is version-stable.

Why it happens

The notebook format has three cell types but agents written against 'cells with source' often assume all sources are code. Raw cells exist precisely to hold non-code text, and their content frequently looks like code (or LaTeX, which looks like line noise). The type field is the format's way of saying 'do not execute this'; ignoring it is ignoring the format.

Edge cases / pitfalls

• Some tools store code-like content in raw cells deliberately (templates). Still do not execute them.
• The filter belongs at the execution boundary, not scattered through helpers. One choke point.
• Markdown cells with python fences are also not executable as cells. Same rule.
• A notebook with no code cells is valid. The agent should handle it gracefully, not crash.
• nbconvert and export tools already skip non-code cells; the filter matters for custom agent execution loops.

Provenance

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

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

Thread query: raw cell mis-identified as code crashed when agent tried to execute it

TL;DR: Raw cells hold unformatted text (often LaTeX or notes) that is not python, so executing one's source raises SyntaxError or worse. The agent must check cell.cell_type == 'code' before executing anything, and treat raw and markdown cells as non-executable by construction. This is a one-line filter that prevents a whole class of crashes.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. 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 dashboard page while checking search results

Use this when

• Work in Search check agent shows this exact symptom: Browser automation failed on dashboard page while checking search results.
• 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 Search check 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: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. 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 Search check 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 dashboard page while checking search results

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 dashboard page when agent tried to check help center search results for an error query error timeout failure

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

Search check 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

The dashboard shows internal search tooling, not reader results, and its dynamic pages fail automation while also measuring the wrong thing.

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: Search check 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_WeTj4y4r87sTXGhL8gHgBw

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

Thread query: browser automation failed on dashboard page when agent tried to check help center search results for an error query error timeout failure

TL;DR: Fix this in Search check agent by acting on the exact symptom first: run the search checks against the public help center search page or search API as a reader would, and drop the dashboard from the check path entirely, since reader results are the ground truth the check exists to measure. 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

A cell that deletes the CSV it reads from will succeed once and then fail forever, and an agent that re-runs it loops on a file that no longer exists. This is a data-safety bug first and a loop bug second: destructive operations must be guarded (check the file exists, refuse to delete inputs, write to a separate output path). Fix the cell so re-execution is safe, then fix the agent to stop retrying destructive failures blindly.

agent loop detected: re-executed a cell that deletes the source csv it reads from, restore failed

Use this when

• An agent re-runs a cell that deletes or overwrites its own input.
• The source file is gone and cannot be restored.
• The loop is: run, file missing, retry, file still missing.

Not for this skill when

• The file was deleted by a human. Restore from backup or version control.
• The cell fails for other reasons. Debug those directly.

Steps

1. Stop the agent immediately to prevent further damage. Verify: no more executions are running.
2. Assess the data loss: check backups, version control, or the source system for the CSV. Verify: you know whether it is recoverable.
3. Rewrite the cell: never delete inputs; write outputs to a separate path; guard with existence checks. Verify: re-running the cell is safe.
4. Add the agent rule: destructive operations require explicit confirmation and are never retried automatically. Verify: the policy is in the agent's runbook.
5. Restore the data from backup and re-run. Verify: the run completes without touching the source.

Variant phrasings

agent deleted input file loop

Short form. Guard destructive cells.

cell deletes its own input csv

The bug phrasing. Separate input and output paths.

agent re-execution data loss

The safety phrasing. Never auto-retry destructive ops.

Compatibility: Any notebook runner. The guard pattern is language-agnostic.

Why it happens

Notebooks mix exploration with file operations, and a cleanup line that made sense once (remove the raw file after processing) becomes a landmine under an agent that re-executes freely. The first run deletes the input; every later run fails on the missing file; the agent retries because retry is its hammer. The deeper failure is that nothing marked the operation as destructive and non-retryable.

Edge cases / pitfalls

• This vertical's framing rule applies: agents must never silently delete user data. Deletion needs explicit user confirmation.
• Backups are the only real safety net. Version the inputs or keep the raw data immutable.
• A 'restore failed' means the damage is done. The lesson goes into the runbook, not just the cell.
• Audit other cells for the same pattern (overwrite-in-place, delete-after-read). Fix them all.

Provenance

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

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

Thread query: agent loop detected: re-executed a cell that deletes the source csv it reads from, restore failed

TL;DR: A cell that deletes the CSV it reads from will succeed once and then fail forever, and an agent that re-runs it loops on a file that no longer exists. This is a data-safety bug first and a loop bug second: destructive operations must be guarded (check the file exists, refuse to delete inputs, write to a separate output path). Fix the cell so re-execution is safe, then fix the agent to stop retrying destructive failures blindly.