Troubleshooting overview
Start here when Fabricator is not working, then jump to the symptom that matches what you see.
Use this page when Fabricator gets stuck, a sign-in fails, a preview is blank, or a deploy does not finish. Start with the checks below, then use the symptom index.
Ask Help first
Fabricator has a built-in assistant that reads the errors it recorded on your computer and explains what went wrong.
- In the status bar, select Help, or press
Ctrl+J(Cmd+Jon macOS). - Describe the problem, such as "why did my last deploy fail?".
Help often identifies the cause faster than working through the index below, because it can see the exact error you hit. See Ask Help.
First steps for any problem
- Update to the latest version. Restart Fabricator so it checks for an update, and install the update if Fabricator offers one. If you installed an old build from before auto-update existed, download and install the latest release once from GitHub Releases. Future updates are in-app.
- Restart Fabricator. This refreshes the bundled Copilot engine, PATH discovery, the preview surface, and any setup checks that depend on tools installed while the app was open.
- Re-check setup. On the setup screen, select Re-check after installing Node.js, Git, Azure CLI, GitHub CLI, or after signing in.
- Check the status bar version. The lower-right status bar shows the Fabricator app version. Include that version in reports.
- Read the exact message. The fastest fix usually depends on the exact quoted error in the banner, modal, chat card, or setup row.
Symptom index
| If you see this | Go here |
|---|---|
| Windows SmartScreen warns about the installer | Windows says the installer is uncommon |
| macOS says the app is damaged | macOS says Fabricator is damaged and can't be opened |
| An update prompt, banner, or manual update problem | An update won't install or keeps prompting |
| A setup tool is missing, outdated, or failed its version check | A tool shows as missing or failed |
| GitHub Copilot sign-in fails | GitHub Copilot sign-in doesn't work |
| Chat asks you to sign in again | Copilot asks you to sign in again |
| Azure CLI is using the wrong tenant or account | Azure CLI is signed in to the wrong account |
| Fabric sign-in does nothing or does not finish | Fabric sign-in doesn't complete |
| Chat shows a Copilot error | Chat shows a Copilot error |
| A chat turn looks stuck | A chat turn seems stuck |
| The chat history changed or a new Copilot session started | The conversation disappeared or a new session started |
| Copilot credits or premium requests run out | Copilot credits run out quickly |
Rayfin CLI reports missing packages such as rxjs, commander, or jsonwebtoken | Rayfin CLI reports missing dependencies |
| Preview is blank, stale, or stuck opening | The preview is blank or stuck |
| Every preview port is taken | All preview ports are busy |
| Preview shows an older app | The preview shows an old version |
| The app inside the preview asks you to sign in | The preview asks you to sign in |
| The local preview says "Automatic local sign-in failed." | The local preview says automatic sign-in failed |
| Preview covers chat or other UI | The preview covers other Fabricator controls |
| Team app local preview restarts | A team app local preview restarts |
| The preview says Deploy failed | A deploy failed |
| Automatic redeploy no longer runs after chat | Automatic redeploy stopped |
| Deploy keeps failing after Fabric sign-in | Fabric authentication blocks deploy |
| Semantic model reads fail | Couldn't read the semantic model |
| Workspace or Fabric capacity blocks deployment | The workspace or capacity blocks deploy |
Rayfin CLI is missing or npm reports ETARGET | Rayfin CLI or npm package resolution failed |
| Someone else cannot open the shared app | Recipients can't open the shared app |
| A team workspace step failed and its message doesn't explain why | A team step failed and the message doesn't explain it |
| A team workspace setup step needs admin help | Setup needs an administrator |
| Team workspace setup can't create the GitHub repository in your organization | Setup can't create the GitHub repository |
| Team workspace setup says the organization locked the repository until it's set up | The organization locked the repository until it's set up |
| A team workspace pipeline's sign-in fails with AADSTS7002381 | The pipeline's sign-in fails with AADSTS7002381 |
| GitHub CLI is missing, signed out, or missing scopes for a team workspace | GitHub CLI is missing, signed out, or missing scopes |
| GitHub says an organization requires single sign-on for a team workspace | GitHub says the organization requires single sign-on |
| A team workspace pipeline or publish run failed | A pipeline failed |
| A team workspace pipeline never starts, or setup says no runner picked it up | No runner picks up the pipeline |
| Team publish is blocked by conflicts | Publish is blocked or has conflicts |
| Team previews are missing, failed, or old | Previews are not deploying |
| A team workspace invitation is missing | Invitations are not showing |
| Team workspace pipeline health says Repair is needed | Repair is needed after updates |
| Any team workspace problem | Team workspace problems |
Get help
If the fix for your symptom does not work, collect diagnostics and open a report:
- In the status bar, select Help.
- Describe the problem, or ask Help to report it for you.
- Select Report this on GitHub, then drag the diagnostics file that Fabricator created onto the issue.
See Report a problem for what Fabricator includes and what to remove before posting publicly.
Team workspace limitations
Understand current team workspace limits for GitHub plans, github.com, Rayfin versions, secrets, and the experiment toggle.
Ask Help
Open the built-in Help assistant to find out why something failed, using your own activity history, the documentation, and the version of Fabricator you are running.