Troubleshooting

If something's wrong, this page is the first stop. Searchable by the error string.

Figma

"Token invalid or insufficient scopes"

  • Confirm the token has File content: Read and File metadata: Read.
  • If your account lost access to the file's team, the token no longer works — regenerate from an account that still has access.

"File too large to ingest"

  • We cap ingestion at ~30 MB of normalized IR. Split the file by Figma page or remove high-resolution image fills before importing.

Dataverse

"AADSTS70011: requested scope is invalid"

  • The Entra ID app needs the Dynamics CRM API permission with user_impersonation, granted by an admin.

"401 from /WhoAmI"

  • You created the app registration but skipped the application user step. Add the app as an application user in your Dataverse environment.

"Client secret expired"

  • Secrets in Entra ID expire after 6, 12, or 24 months. Issue a new secret and paste it into Settings → Integrations → Dataverse.

Generation

"Task failed: invalid Liquid"

  • Click Retry — the AI usually fixes itself on the second pass. If it fails repeatedly on the same frame, simplify the bindings or split the frame.

Fidelity stuck below 70

  • Check that every bound layer has a matching column type — coercion failures hurt binding coverage.
  • Frames over ~400 leaves stress the IR-leaf coverage metric. Split them.

Packaging

"Validation failed: duplicate template name"

  • Two Figma components produced the same kebab-case slug. Rename one in Figma and re-ingest, or rename in the components panel before building the package.

Deploy

"pac paportal upload: 403"

  • The signed-in user (or service principal) is missing the System Administrator or Power Pages Administrator role in the target environment.

Changes don't appear after upload

  • Power Pages caches aggressively. Re-run the upload with --modelVersion 2 --deploymentProfile prod or wait a few minutes.
Still stuck?
Send us the task ID, package ID, or audit event ID — we can look up the run in our logs and respond with a fix or a diagnosis. Contact: /contact.
Was this page helpful?Send feedback →