How do I debug failed attempts?

If something goes wrong during auto-provisioning, Cakewalk flags the failure in the Provisioning tab under App Governance. You’ll see a summary of how many tasks succeeded and how many failed—per app.

This lets you quickly spot issues without digging through logs.

Where to Find Errors

1. Go to App Governance.

2. Select the app you want to review (e.g. Miro).

3. Click the Provisioning tab.

• Go to App Governance.

• Select the app you want to review (e.g. Miro).

• Click the Provisioning tab.

You’ll see the number of successful and failed provisioning runs.

• You’ll see the number of successful and failed provisioning runs.

If any runs failed, an error label will appear.

• If any runs failed, an error label will appear.

Click the info icon (i) for context and next steps.

• Click the info icon (i) for context and next steps.

Common Reasons for Failures

Here are the most typical failure scenarios—and what to do next:

🔧 The permission is invalid

The permission selected for auto-provisioning (e.g. Admin, Viewer, Editor) might not exist in the third-party app or is spelled differently.

What to do: Go to the Permissions section in Cakewalk of the corresponding app and adjust the permission settings to match those of the third-party app. Afterwards, recreate the configuration.

🔑 The configuration is incomplete or incorrect

Sometimes, access credentials, API keys or required metadata are incorrect or missing. This can block provisioning.

What to do: Recreate the configuration for that app from scratch. Double-check that:

• Admin access is granted

• API keys or secrets are correct

• Any required setup steps in the app were completed

👤 The user already exists

Provisioning is skipped because the user already has access in the app.

No action needed: This isn’t an error. Cakewalk simply skips the request and keeps the configuration active.