Skill ID Not Found when Deploying a Skill
This error happens when you try to deploy a skill that was previously deployed, but has since been deleted.
When you deploy a skill, it will be assigned a skill ID that is written along with some other deployment artifacts to the .ask directory in the skill’s project directory. In order to get past this error, you’ll need to delete the .ask directory. On a Unix-based operating system you can delete it like this:
| | $ rm -rf .ask |
The next time you deploy the skill, it will be assigned a new, fresh skill ID.
Also, the URI of the AWS Lambda function which is the skill’s fulfillment is also written to the /skill-package/skill.json file. For example, if you open the skill.json file, you might see the following endpoint property as a child of apis.custom:
| | "apis": { |
| | "custom": { |
| | "endpoint": { |
| | "uri": "arn:aws:lambda:us-east-1:494442948374: |
| | function:ask-starport-75-default-default-1625712152087" |
| | } |
| | } |
| | }, |
You’ll need to clear this URI, or else it will be deployed to try to use the old AWS Lambda function from the previous deployment. The skill.json file has other useful information in it, so you can’t simply delete the file. But you can remove the endpoint property so that section of skill.json looks like this:
| | "apis": { |
| | "custom": {} |
| | }, |
Now if you try to redeploy your skill, it should be able to deploy successfully and be assigned a new skill ID.