Resolve Hub permissions, approval, delivery and workflow errors
Find the affected layer, preserve the current resource revision and resolve the actual cause before repeating an action.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Affected resource or record → history; Automation → Enrolment history / Delivery queue
PermissionAccess to the affected object; relevant management capability for a correction
Before you begin
Start with the resource, record or run reference and the exact message. Keep client data, submission payloads, mailbox content and secrets out of a public support request.
Follow these steps
- Check the intended workspace, current staff identity, native record access and relevant Hub capability.
- For a save conflict, reload the current revision and apply only the intended edit. For approval, use a reviewer different from the last editor.
- For publication, check matching current approval, valid links and published dependency revisions.
- For an automation problem, inspect the run’s initiator, source, state, due time, execution hours, completion goal and history. For email, inspect the existing queue row and consent/suppression checks.
- After correcting the cause, repeat only the appropriate action. Record the reference and verified result rather than creating a second unexplained run or delivery.
Fields and options
- Useful support context
- Workspace, object/reference, staff role, UTC time, exact redacted error and the check already performed.
- Unavailable dependency
- An inactive native module or unavailable mailbox is not created by opening the Hub.
- Scope
- Registers, histories and reports are permission-aware and bounded. A count or sample is not a complete unrestricted export.
Rules and limits
- Do not retry an Uncertain delivery automatically; check the SMTP/provider outcome first.
- The Hub does not infer consent, certify legal compliance, send internal draft activities as email or implement external ad publishing.
- A dry run or Launch Rehearsal proves only the evaluated definition and sample, not live external delivery.
Check the result
- Confirm the original issue is resolved on the correct object and current revision.
- Check the action did not create duplicate enrolments, messages or native tasks.
If something does not look right
- If a worker-dependent action waits, check the normal CRM cron and its due time before changing data.
- If an error remains, share the redacted reference and exact message with support; do not share full encrypted payloads or credentials.
Common questions
Should I give every user administrator access to fix missing buttons?
No. Check the specific capability, ownership and native record access.
Can I assume a successful preview means an email was sent?
No. Preview and dry-run tools make no external send. Inspect the real queue and verify the external result separately.