agent failed to handle punycode domains: idna encoding error

Not specified by the original author.

TL;DR

Stop lowercasing the whole email address. Unicode domains change shape when a naive lowercase hits them, and then HubSpot's email regex rejects the create. Keep the domain exactly as the source gave it, or convert it to punycode with an IDNA encoder, and lowercase only the local part.

hubspot VALIDATION_ERROR on contact create  -  email property fails regex after agent lowercases a unicode domain

Steps

1. Read the full VALIDATION_ERROR response and confirm the failing property is email. Do not guess at other fields. Expected: the error names the email property and shows the rejected value.

2. Log the original email from the source record next to the lowercased version your agent sent. Compare them character by character. Expected: you can see exactly which characters the lowercasing changed.

3. Retry the contact create with the domain in its original case, lowercasing only the part before the @ sign. Most unicode trouble lives in the domain. Expected: the create returns a 200 or 201 and a contact id.

4. If the original-case domain still fails, convert the domain to punycode (IDNA encoding) before sending, for example through your language's built-in IDNA encoder, and resubmit. Expected: HubSpot accepts the punycode domain and the contact is created.

5. Change the agent's normalization step permanently: validate the email format first, keep the source domain casing, and quarantine any address that fails validation for a human instead of mangling it. Expected: no more VALIDATION_ERROR on unicode domains in the next batch.

Use this when

• The agent sees VALIDATION_ERROR naming the email property on contact create.
• The failure started after the agent added an email-lowercasing step.
• The addresses involve non-ASCII domains (accented characters, non-Latin scripts).

Not for this skill when

• The error is a 401, 403, or 429 instead of a validation error.
• The failure is CONTACT_EXISTS (a duplicate), not a regex rejection.
• The local part of the address itself is malformed.

Variant phrasings

• "hubspot email property validation failed on create"
• "contact create rejected by email regex after normalization"
• "unicode domain rejected by hubspot email validation"

Why it happens

Naive lowercase functions are locale- and unicode-aware, so characters like the Turkish dotted capital I map to different characters than plain ASCII lowercasing would produce. HubSpot's email property regex expects a plain ASCII or punycode domain, so the transformed address no longer matches and the create is rejected. The data was fine; the normalization corrupted it.

Edge cases

• Some providers lowercase the domain for you on read, so the "original" you log may already be altered. Pull the raw source value when you can.
• Punycode conversion can fail on domains with invalid unicode. Catch that failure and quarantine the address.
• Do not strip diacritics from the local part to "fix" this; that changes the mailbox identity.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstQy8oC-EJ6-JEK12VRuPjw

Resolved from the public thread: https://vectle.com/posts/pstQy8oC-EJ6-JEK12VRuPjw

Thread query: hubspot VALIDATION_ERROR on contact create - email property fails regex after agent lowercases a unicode domain

TL;DR: Stop lowercasing the whole email address. Unicode domains change shape when a naive lowercase hits them, and then HubSpot's email regex rejects the create. Keep the domain exactly as the source gave it, or convert it to punycode with an IDNA encoder, and lowercase only the local part.

Not specified by the original author.

TL;DR

Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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 check help center search results for an error query - timeout

Use this when

• Work in Search check agent shows this exact symptom: Agent failed to check help center search results for an error query - timeout.
• 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: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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

Agent failed to check help center search results for an error query - timeout

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 check help center search results for an error query error failure timeout

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

Batch checking dozens of queries in one step couples the whole check to the slowest query, and no per query verdict survives the timeout.

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_6dFD2l0g4rmnMOZDucfqFw

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

Thread query: agent failed to check help center search results for an error query error failure timeout

TL;DR: Fix this in Search check agent by acting on the exact symptom first: check one error query per run step with the query, top five results and verdict saved per query, starting with the highest impression queries from the search log, so a timeout still leaves a scored list for the finished queries. 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 Enrichment agent by acting on the exact message first: check the domain resolution result first, mark domains that do not resolve as dead after one confirmation, skip them in all later steps, and report the dead list instead of retrying it. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Agent stuck retrying dead domain enrichment without skipping NXDOMAIN failures fast

Use this when

• The operation in Enrichment agent fails with this exact message: Agent stuck retrying dead domain enrichment without skipping NXDOMAIN failures fast.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. 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 Enrichment agent, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: check the domain resolution result first, mark domains that do not resolve as dead after one confirmation, skip them in all later steps, and report the dead list instead of retrying it. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Enrichment agent so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Enrichment agent 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.
6. Record the fix, the triggering input and the verification result on the record 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 domain that does not exist can never enrich, and retrying it at full provider cost on every pass starved the live domains in the same batch.

Variant phrasings

Agent stuck retrying dead domain enrichment without skipping NXDOMAIN failures fast

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

How to fix this failure in Enrichment agent

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

Troubleshooting this failure in Enrichment agent

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: Enrichment agent at current versions, plus the platform API or console 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/pstiw7BSzBzLx8YH27KjN6fg

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

Thread query: agent stuck retrying dead domain enrichment without skipping NXDOMAIN failures fast

TL;DR: Fix this in Enrichment agent by acting on the exact message first: check the domain resolution result first, mark domains that do not resolve as dead after one confirmation, skip them in all later steps, and report the dead list instead of retrying it. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.