Studio FAQ and Troubleshooting

Q: Something is confusing or isn’t working. What should I try first?

A: Ask Studio in the chat. Describe what you see and what you expected. Studio can explain most issues and suggest the next step.

Q: What’s the difference between the User Plan and the Technical Plan?

A: The User Plan describes what your plugin will do in plain language. Review it to confirm Studio understood your requirements. The Technical Plan contains the technical details of how the plugin will be built. You don’t need to review it unless you want those details.

Q: Why did a document change while I was reading it?

A: Studio updated the document. If you see a reload prompt in its tab, use it to view the latest version.

Q: Why isn’t the Deploy or Publish button showing?

A: Buttons appear when the requirements for each stage are met. For example, Deploy Now for Testing requires a completed build, a testing plan, and any required configuration. If Publish is missing during Final Review, see Publishing and Updating Studio Plugins.

Q: Why does a saved configuration value look blank?

A: Studio hides sensitive values after saving them for security. Value set - leave blank to keep, type to replace means your value is still saved. Enter a new value only if you want to replace it.

Q: Why can’t my colleague send messages in a shared project?

A: They likely have View-only access. The project owner can change their permission to Full editing.

Q: What does “Another collaborator’s request is in flight” mean?

A: Another collaborator has a request running. Studio handles one request at a time. Wait for it to finish, then resend your message.

Q: What does the orange “Deploy unverified” status mean?

A: Studio couldn’t confirm whether the plugin deployed successfully. Ask the assistant to try deploying again.

Q: Why won’t my attachment send?

A: Each message supports up to 10 MB of attachments. If you're uploading multiple files, try sending them separately.