Help ⁉️

Common Issues

The IssueThe ReasonThe Solution
“Well shoot! You don’t have access to emit example-example-example::v202x_xx_xx” when booting a Skill.This is happening because your Skill is not properly authenticated with Mercury.You need to make sure the SKILL_ID and SKILL_API_KEY in your Skill's .env matches what is in Mongo. If you have never registered your skill, cd to your Skill and try spruce register. If you have already registered your skill, but lost the .env, cd to your Skill and try spruce login.skill. If you are in a Theatre and your skill is part of the Theatre, you can rerun yarn setup.theater blueprint.yml and it will try both spruce register and spruce login.skill for each skill for you.
“MercurySocketIoClient :: Failed to connect to Mercury I couldn’t connect to http://127.0.0.1:8081. The code I got back was 503.”Mercury is not running!Make sure your Theatre is booted. cd to your Theatre and run yarn boot. Or, if you setup the Development Theatre, just open it.

Something Missing?

Request Documentation Enhancement
It looks like you are using Internet Explorer. While the basic content is available, this is no longer a supported browser by the manufacturer, and no attention is being given to having IE work well here.