After askx deploy-ed, the console building of the model fails.

[maxipesfix]

Converted a skill to V2 CLI, added connections task and askx deployed. Now when building the model on the alexa console getting this error: Definition for tasks in skill manifest not found.

[RonWang]

Hi @maxipesfix

Do you see any error during the process of askx deploy? And does this error message only happen when you build your model (does it happen when you update any other data on the console)?

Thanks,
Ron

[maxipesfix]

yes the was error on deployment (below). However after cloning the skill again, the task appears to be a part of the skill package.

Updating products on the console, for example, did not cause the error: I could link/unlink a product without an issue.

Thanks

$ askx deploy

==================== Deploy Skill Metadata ====================
[Error]: {
"skill": {
"resources": [
{
"action": "DISASSOCIATE",
"name": "InSkillProduct:amzn1.adg.product.02811cac-63b2-48fb-b295-ff657871d71d",
"status": "ROLLBACK_SUCCEEDED"
},
{
"action": "DISASSOCIATE",
"name": "InSkillProduct:amzn1.adg.product.812541ff-648a-49e3-9766-941eef8de295",
"status": "ROLLBACK_SUCCEEDED"
},
{
"action": "DISASSOCIATE",
"name": "InSkillProduct:amzn1.adg.product.984e9b2b-82b5-41fc-aff2-d88c602bf2c7",
"status": "ROLLBACK_SUCCEEDED"
},
{
"action": "DISASSOCIATE",
"name": "InSkillProduct:amzn1.adg.product.d8ae2910-f7d4-49b2-b0a8-c891e83cce52",
"status": "ROLLBACK_SUCCEEDED"
},
{
"action": "ASSOCIATE",
"errors": [
{
"message": "In-skill product is already associated with this Skill."
}
],
"name": "InSkillProduct:amzn1.adg.product.f60b361a-812d-412d-a5a2-f8a002fd219a",
"status": "FAILED"
},
{
"action": "UPDATE",
"name": "InteractionModel.en-US",
"status": "ROLLBACK_IN_PROGRESS"
},
{
"action": "UPDATE",
"name": "Manifest",
"status": "SUCCEEDED"
},
{
"action": "CREATE",
"name": "TaskDefinitions",
"status": "SUCCEEDED"
}
],
"skillId": "amzn1.ask.skill.09227ade-b48d-4325-bc71-bc694d998cd9"
},
"status": "FAILED"
}

[RonWang]

Based on your description, it seems the create of ISP failed

{
"action": "ASSOCIATE",
"errors": [
{
"message": "In-skill product is already associated with this Skill."
}
],
"name": "InSkillProduct:amzn1.adg.product.f60b361a-812d-412d-a5a2-f8a002fd219a",
"status": "FAILED"

But I wondered why manifest and task are not rollback. And this might cause task not found error. I will forward this issue to our service team. And could you try use "askx api get-task" api command and see if this task can be retrieved?

[RonWang]

In addition, to help us better debug your issue, could you reproduce the issue by trying to askx deploy again with --debug flag? We need to check why this import-package API request fails. This will show the necessary information for that SMAPI request. Make sure no sensitive data exposed, and requestId provided.

[RonWang]

As there are some user specific data from reporter @maxipesfix I deleted his reply and summarized it as below:

Thanks for looking into this. The api get-task and deploy --debug outputs are below.

Cheers,
maxim

$ askx api get-task -s amzn1.ask.skill.09227ade-b48d-4325-bc71-bc694d998cd9 -t "StartTask" -v "1"
[Error]: {
"message": "Task Name is invalid"
}

$ askx deploy --debug
==================== Deploy Skill Metadata ====================
[Error]: {
"skill": {
"resources": [
{
"action": "ASSOCIATE",
"errors": [
{
"message": "In-skill product is already associated with this Skill."
}
],
"name": "InSkillProduct:amzn1.adg.product.f60b361a-812d-412d-a5a2-f8a002fd219a",
"status": "FAILED"
},
{
"action": "UPDATE",
"name": "InteractionModel.en-US",
"status": "ROLLBACK_SUCCEEDED"
},
{
"action": "UPDATE",
"name": "Manifest",
"status": "ROLLBACK_SUCCEEDED"
},
{
"action": "UPDATE",
"name": "TaskDefinitions",
"status": "ROLLBACK_SUCCEEDED"
}
],
"skillId": "amzn1.ask.skill.09227ade-b48d-4325-bc71-bc694d998cd9"
},
"status": "FAILED"
}

The failure import-package and its request-id:
[2020-02-03T22:19:16.053Z] - DEBUG - IMPORT-PACKAGE
request-id: 3a9519bb-f6cc-4f3b-a420-53876e5232df

[RonWang]

@maxipesfix based on your deploy failure message, it's because of In-skill product is already associated with this Skill. that causes the rollback of all skill package resources.

To unblock you first, we might need to see why this in-skill product is not allowed to be associated to your skill. Instead of using existing isp-id, could you create a new isp during the deploy flow? You might find this link useful. Try to see if you could deploy after solving the isp failure to make your skill back to normal. I've also forwarded your reply to our service team and will update here if we figured why.

[maxipesfix]

I removed product associations, redeployed, and then added the associations again. It appears that fix the console building error.

However the get-task still returns "Task name is invalid" while cloning does retrieve the task JSON.

[RonWang]

Cool @maxipesfix ~ It might be because the first time import fails and the created task also got deleted. I will keep talking with our backend service to improve the So that task-id is not an existing resource anymore. Since you are unblocked now, I will close this issue. Feel free to let us know if there is any problem!