Resolve failed provisioning jobs
Inspect attempt count, last error, generated configuration and permissions/path ownership.
Exact navigationAdmin Area → Setup → xConnect
Before you begin
- Confirm the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide covers
Inspect attempt count, last error, generated configuration and permissions/path ownership. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Admin Area → Setup → xConnect.
- Locate the record, setting or action used to resolve failed provisioning jobs.
- Complete the displayed fields or controls exactly as described in this guide.
- Select the available save, submit, update, call, sign, upload or confirm action.
- Return to the related register, portal, dashboard or call panel and verify the recorded result.
Fields, choices and supported possibilities
IssueInspect attempt count, last error, generated configuration and permissions/path ownership.
Code-backed validations and workflow rules
- Use the actual failure code, readiness evidence and scope boundaries; do not bypass tenant or security controls.
Expected result and verification
- The resolve failed provisioning jobs workflow completes without a validation, permission or availability error.
- The relevant case, document, proposal, call, extension, widget session, timeline or audit evidence shows the expected state.
- Any client-visible or public result appears only where the code explicitly allows it.
Security, privacy and operational checks
- Use a controlled test case, contact, extension or website origin before production rollout.
- Grant the minimum permissions needed and protect private documents, call metadata, signing evidence, API credentials and infrastructure paths.