DupliCat Troubleshooting

This page is for operator triage: quick checks, clear boundaries, and what to send to support when you’re stuck.

Operator index

Before you escalate

Confirm you’re in the correct HubSpot portal/account.
Confirm the object type is supported for the path you used (for example Deal/Contact/Company/Ticket/Order/Project on current record-view or workflow paths).
Capture a timestamp with timezone and any visible error text.
If you used templates/defaults, note the template name (or whether you used Use effective default).
If you used workflow cloning, capture the workflow name and run context from workflow history.

Boundaries (quick reminders)

Card runs are capped at Number of duplicates (1-10) per execution.
Associations are re-linked by default; deep cloning is limited to deal line_items when selected.
Activity-object cloning and related-activity copying are supported in DupliCat, but attachments are not cloned.

Common signals and what to do

Signal string / condition	What to do now
Install authorization fails	Re-run install and confirm the app is connected for the intended portal.
Settings page won’t load or save	Retry once, then capture screenshots + timestamp/timezone and escalate with portal ID.
Card does not appear on a record	Re-open record view customization for that object type and confirm the DupliCat card is added and published.
Preview card does not appear	Confirm the DupliCat preview card is added and published for that object type’s preview surface.
Template missing	Re-select your template and confirm it still exists for this portal and object type.
Template/object mismatch	Confirm your record/workflow object type matches the template object type (`CONTACT`, `COMPANY`, `DEAL`, `TICKET`, `ORDER`, `PROJECT`, or the object family you configured).
Defaults not loading as expected	Confirm portal default and personal default (“my default”) settings for that object type, then retry with Use effective default.
Clone fails with invalid field errors	Enable writable-only mode and add the field to skip fields, then retry one controlled clone.
Clone fails with unique-field conflicts	Adjust the conflicting source values (e.g., email/domain) or skip that field, then rerun.
Deal line items expected but missing	Confirm you selected `line_items` for that run; otherwise DupliCat re-links associations instead of deep cloning.
Workflow action expected but unavailable	Confirm the workflow action is added for the correct object type and the app install/scopes are still active.
Workflow run completed with “needs attention”	Review workflow output details and confirm input values and IDs are valid; rerun one controlled test.
`Permission denied` / scope failures	Confirm required scopes are approved and the install is still active for the portal.
Missing source-reference note on clone	Note writing is enabled by default; if it’s missing, capture a clone URL + timestamp/timezone and escalate to support.
Field-level mismatch after clone	Validate expected values in HubSpot Property history before changing template/default behavior.

What to include in support intake

Portal ID
Object type (Deal/Contact/Company/Ticket)
Source record URL
Surface used (card: sidebar/preview, or workflow)
Template name (or “Use effective default”)
Number of duplicates value
Timestamp with timezone
Screenshots of workflow output or clone result panel

If escalation is needed, contact support with the above checklist.