Help ⁉️
Common Issues
"Well shoot! You don't have access to emit `example-example-example::v202x_xx_xx`" when booting a `Skill`
Reason
This is happening because your Skill is not properly authenticated with Mercury.
Solution
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."
ReasonMercury is not running!
Solution
Make sure your Theatre is booted. cd to your Theatre and run yarn boot. Or, if you set up the Development Theatre, just open it.
$ node build/index node:internal/modules/cjs/loader:1146 throw err; ^ Error: Cannot find module '#spruce/skill'
Reason This can happen if building fails.
Solution Make sure you have run yarn build in your Theatre or directly in your Skill or module and that it completes without errors.
Duplicate schema -> 'Mercury.messageTemplateAddons(version: v2020_12_25)'.
Reason This happens when multiple versions of the same dependency are loaded via yarn. The @sprucelabs/schema module is set to throw if it detects multiple versions of the same schema being included to avoid ambiguity.
Solution (Theatre Runyarn run update to see if pulling the latest dependencies fixes the issue.
Solution (Skill) Start by running yarn run update in the Skill directory. If that doesn’t work, run spruce upgrade to ensure you actually have the latest dependencies.
