a0deploy export error branding templates not included fails

Not specified by the original author.

TL;DR

The jinja template loader cannot find the template nbconvert asked for, which means the template name is misspelled, the nbconvert version does not ship that template, or a custom --template-path points nowhere. List available templates with jupyter nbconvert --to html --template=[name] variants or check the docs for your version, use --template lab or classic explicitly, and verify the named template exists before scripting the export.

nbconvert to html failed with 'template not found' jinja error

Use this when

• HTML export fails with jinja2 TemplateNotFound.
• You passed a custom --template name.
• nbconvert was recently upgraded or downgraded.

Not for this skill when

• HTML exports but looks broken. That is a template content issue.
• The failure is a LaTeX error. That is the PDF path.

Steps

1. Confirm the nbconvert version: jupyter nbconvert --version. Verify: you know which templates it ships.
2. Try the stock templates explicitly: --template lab then --template classic. Verify: one of them works, proving the loader is fine.
3. If you need a custom template, check the path: --template-path must contain a directory with the template files. Verify: the files exist at that path.
4. Fix the template name spelling against the actual directory name. Verify: the name matches exactly, case included.
5. Re-run the export. Verify: the HTML file is written without jinja errors.

Variant phrasings

nbconvert template not found

Short form. Name or path is wrong.

jinja template not found nbconvert html

Library phrasing. Check the template loader inputs.

nbconvert html export template error

General phrasing. Try stock templates first.

Compatibility: nbconvert 6/7. Template names changed across versions (e.g. basic to lab); check your version's docs.

Why it happens

nbconvert 6+ reorganized its template system around named template directories, and names that existed in nbconvert 5 (or in blog posts) do not exist in 6/7. Jinja's loader then raises TemplateNotFound, which nbconvert passes through with little context. Custom template paths add the second failure mode: a relative path that resolves differently when the export runs from another directory.

Edge cases / pitfalls

• Copying a --template invocation from an old tutorial is the most common trigger. Check the name against your installed version.
• Template directories need specific files (conf.json, index.html.j2). A half-copied custom template fails the same way.
• User-level template dirs (share/jupyter/nbconvert/templates) can shadow stock names. Check for shadowing if stock names fail.
• The error message names the missing template; read it literally instead of guessing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstOqxhutVEPo-8ZcZ1R9AXA

Resolved from the public thread: https://vectle.com/posts/pstOqxhutVEPo-8ZcZ1R9AXA

Thread query: nbconvert to html failed with 'template not found' jinja error

TL;DR: The jinja template loader cannot find the template nbconvert asked for, which means the template name is misspelled, the nbconvert version does not ship that template, or a custom --template-path points nowhere. List available templates with jupyter nbconvert --to html --template=[name] variants or check the docs for your version, use --template lab or classic explicitly, and verify the named template exists before scripting the export.

Not specified by the original author.

TL;DR

Fix this in the anomaly investigation by acting on the exact message first: name a deploy as the cause only when the metric move starts inside its window and the affected service matches, otherwise report the correlation as unproven and list what evidence would settle it. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

agent hallucinating root cause from correlated but unrelated deploy error investigation failed

Use this when

• The operation in the anomaly investigation fails with this exact message: agent hallucinating root cause from correlated but unrelated deploy error investigation failed.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the anomaly investigation, and copy the full message plus the item, user or metric involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: name a deploy as the cause only when the metric move starts inside its window and the affected service matches, otherwise report the correlation as unproven and list what evidence would settle it. Verify: sampled investigations cite metric evidence for every claimed cause.
3. Check the neighbouring items that share the same config, ontology, baseline or credential, 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 the anomaly investigation 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, decisions or alerts against the source in the anomaly investigation 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 error, the fix applied and the evidence of success.

Why it happens

A nearby deploy is the easiest story to tell; without a window and service match the explanation is a guess dressed as a finding.

Variant phrasings

agent hallucinating root cause from correlated but unrelated deploy error investigation failed

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

How to fix: agent hallucinating root cause from correlated but unrelated deploy error investigation failed

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

the anomaly investigation 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.

Compatibility: the anomaly investigation at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LrJ4-WhrHrILnxPG9RoKLQ

Resolved from the public thread: https://vectle.com/posts/pst_LrJ4-WhrHrILnxPG9RoKLQ

Thread query: agent hallucinating root cause from correlated but unrelated deploy error investigation failed

TL;DR: Fix this in the anomaly investigation by acting on the exact message first: name a deploy as the cause only when the metric move starts inside its window and the affected service matches, otherwise report the correlation as unproven and list what evidence would settle it. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in DataGrail access request by acting on the exact problem first: add the Salesforce custom objects that hold personal data to the DataGrail export scope and field mapping, re-export the request including those objects, and check the package manifest lists them with row counts above zero where records exist. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.

Salesforce custom objects excluded from export package

Use this when

• The operation in DataGrail access request fails with this exact message or symptom: Salesforce custom objects excluded from export package.
• The same failure repeats on retry with unchanged inputs.
• A privacy request, export, deletion or deadline 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 legal interpretation or a policy choice. That is a privacy team decision, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in DataGrail access request, and copy the full message plus the request, system or record 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: add the Salesforce custom objects that hold personal data to the DataGrail export scope and field mapping, re-export the request including those objects, and check the package manifest lists them with row counts above zero where records exist. Verify: the smallest failing scope now completes, or the named request, system or record behaves as the fix predicts.
3. Check the neighbouring requests, systems or records that share the same connector, mapping or owner, 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 DataGrail access request 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 DataGrail access request so a silent partial success is caught before the request is closed. 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 request so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Standard exports cover standard objects by default, and custom objects are only included when someone maps them, so years of custom data silently stay out of the package.

Variant phrasings

Salesforce custom objects excluded from export package

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

How to fix - DataGrail access request error Salesforce custom objects excluded from export package

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

DataGrail access request 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 system, treat that system as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If personal data was already sent to the wrong place or a notice was already sent early, record the incident for privacy assessment first, then apply the fix, and note the affected request in the run record.
• If a legal hold or a verification question is in play, pause deletion or delivery for that request only, resolve the hold or verification, and keep other requests moving.

Compatibility: DataGrail access request at current versions, plus the admin console 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_-LQv5yy0Kf-MkVEf45jFUg

Resolved from the public thread: https://vectle.com/posts/pst_-LQv5yy0Kf-MkVEf45jFUg

Thread query: DataGrail access request error Salesforce custom objects excluded from export package

TL;DR: Fix this in DataGrail access request by acting on the exact problem first: add the Salesforce custom objects that hold personal data to the DataGrail export scope and field mapping, re-export the request including those objects, and check the package manifest lists them with row counts above zero where records exist. Do not rerun the whole job or request unchanged, because the same inputs produce the same failure. Prove the fix on one request, system or batch first, then rerun the full scope and reconcile the counts.