SOLVED

Skills: Simple Bot to Bot and Skills Dialog

%3CLINGO-SUB%20id%3D%22lingo-sub-1385205%22%20slang%3D%22en-US%22%3ESkills%3A%20Simple%20Bot%20to%20Bot%20and%20Skills%20Dialog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1385205%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EWe%20came%20across%20the%20Bot%20Service's%20Skills%20concept%20at%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbot-service%2Fskill-implement-skill%3Fview%3Dazure-bot-service-4.0%26amp%3Btabs%3Dcs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbot-service%2Fskill-implement-skill%3Fview%3Dazure-bot-service-4.0%26amp%3Btabs%3Dcs%3C%2FA%3E.%26nbsp%3B%20We%20cloned%20the%20Bot%20Samples%20and%20tried%20running%20both%20the%20Simple%20Bot%20to%20Bot%20and%20SkillsDialog%20samples.%26nbsp%3B%20Both%20are%20giving%20us%20the%20following%20errors%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%5BonTurnError%5D%20Exception%20caught%20in%20sendErrorMessage%3A%20Error%3A%20%2Fapi%2Fmessages%2Fv3%2Fconversations%2Fd24ed016-6872-4a57-bd99-c93aa061e32c-8b8cc16a-597d-4bae-a4e0-b992af4d9b38-a%3A11XpYDC7setK3n4POxpFnsvU_143zXeMzsTqFuspVzDeE5fmF02wN0tqvWdvSjd89cdG9f7RWm-Gr76RV8z-Ny3j4NM24noCOmWV7zUxqqBbyc6SILj8Fkz0iW2l2HYHN-msteams-skillconvo%2Factivities%2F1589352227371%20does%20not%20exist%0A%0A%20%5BonTurnError%5D%20Exception%20caught%20in%20sendEoCToParent%3A%20Error%3A%20%2Fapi%2Fmessages%2Fv3%2Fconversations%2Fd24ed016-6872-4a57-bd99-c93aa061e32c-8b8cc16a-597d-4bae-a4e0-b992af4d9b38-a%3A11XpYDC7setK3n4POxpFnsvU_143zXeMzsTqFuspVzDeE5fmF02wN0tqvWdvSjd89cdG9f7RWm-Gr76RV8z-Ny3j4NM24noCOmWV7zUxqqBbyc6SILj8Fkz0iW2l2HYHN-msteams-skillconvo%2Factivities%2F1589352227371%20does%20not%20exist%3C%2FCODE%3E%3C%2FPRE%3E%3CDIV%3E%3CDIV%3EIt%20feels%20like%20the%20root%20bot%2Froot%20dialog%20was%20able%20to%20send%20a%20Skill%20request%2Factivity%20to%20the%20skill%20bot%2Fskill%20dialog%20but%20the%20skill%20bot%2Fskill%20dialog%20was%20not%20able%20to%20reply%20back%20to%20the%20conversation%20because%20the%20conversation%20could%20not%20be%20found.%26nbsp%3B%20Has%20anyone%20come%20across%20this%3F%26nbsp%3B%20How%20did%20you%20resolve%20this%3F%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EThank%20You%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1385205%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1388422%22%20slang%3D%22en-US%22%3ERe%3A%20Skills%3A%20Simple%20Bot%20to%20Bot%20and%20Skills%20Dialog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1388422%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F493333%22%20target%3D%22_blank%22%3E%40voonsionglum%3C%2FA%3E%26nbsp%3B%2C%20Did%20you%20implemented%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbot-service%2Fskill-implement-skill%3Fview%3Dazure-bot-service-4.0%26amp%3Btabs%3Dcs%23to-continue-or-complete-a-conversation%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Econversation%20for%20skill%3C%2FA%3E%3F%20You%20can%20take%20a%20look%20at%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbot-service%2Fskill-implement-skill%3Fview%3Dazure-bot-service-4.0%26amp%3Btabs%3Dcs%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EImplement%20the%20skill%3C%2FA%3E%20in%20Teams%20Skills%20Bot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1388446%22%20slang%3D%22en-US%22%3ERe%3A%20Skills%3A%20Simple%20Bot%20to%20Bot%20and%20Skills%20Dialog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1388446%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F371090%22%20target%3D%22_blank%22%3E%40Trinetra-MSFT%3C%2FA%3E%2C%26nbsp%3Bthanks%20for%20responding.%26nbsp%3B%20The%20conversation%20for%20skill%20was%20implemented%20for%20the%20echo-skill-bot.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20the%20root%20bot%20sends%20the%20skill%20activity%20to%20the%20echo-skill-bot%2C%20I%20can%20see%20that%20the%20latter%20did%20get%20the%20activity.%26nbsp%3B%20When%20the%20echo-skill-bot%20tries%20to%20send%20the%20reply%20to%20the%20root%20bot%2C%20it%20errors%20out%20saying%20that%20the%20conversation%20it%20tries%20to%20reply%20to%20does%20not%20exist.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20printing%20out%20the%20context%20when%20that%20error%20happens.%26nbsp%3B%20I%20can%20see%20that%20the%20conversation%20Id%20and%20the%20activity%20Id%20in%20the%20context%20match%20with%20the%20ones%20thrown%20by%20the%20error%2C%20but%20I%20don't%20know%20why%20the%20conversation%20does%20not%20exist.%26nbsp%3B%20It%20feels%20like%20something%20is%20missing...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1392045%22%20slang%3D%22en-US%22%3ERe%3A%20Skills%3A%20Simple%20Bot%20to%20Bot%20and%20Skills%20Dialog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1392045%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20some%20more%20information.%26nbsp%3B%20I%20am%20running%20the%20simple-root-bot%20locally%20and%20opening%20it%20with%20the%20Bot%20Framework%20Emulator%20at%20port%203978.%26nbsp%3B%20I%20am%20running%20the%20echo-skill-bot%20locally%20at%20port%2039783.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20Emulator%2C%20when%20I%20type%20in%20%22skill%22%2C%20the%20simple-root-bot%20responds%20with%20%22%3CSPAN%3EGot%20it%2C%20connecting%20you%20to%20the%20skill%E2%80%A6%22.%26nbsp%3B%20I%20updated%20my%20rootBot.js%20so%20that%20before%20the%20%22%3C%2FSPAN%3E%3CSPAN%3Eawait%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Ethis%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3CSPAN%3EsendToSkill%3C%2FSPAN%3E%3CSPAN%3E(%3C%2FSPAN%3E%3CSPAN%3Econtext%3C%2FSPAN%3E%3CSPAN%3E%2C%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Ethis%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%3CSPAN%3EtargetSkill%3C%2FSPAN%3E%3CSPAN%3E)%3B%22%20in%20the%20%22onMessage%22%20is%20called%2C%20I%20print%20out%20the%20context%20and%20the%20the%20target%20skill.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20context%20shows%20the%20following%20conversation%20Id%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3Econversation%3A%20%7B%20id%3A%20'fc9260e0-966b-11ea-9510-8344e3862407%7Clivechat'%20%7D%2C%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20targetSkill%20object%20has%20the%20following%20values%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%7B%20id%3A%20'EchoSkillBot'%2C%0A%20%20appId%3A%20'aaebe6ed-b0ee-4487-92b7-xxxxxxxxxxxx'%2C%0A%20%20skillEndpoint%3A%20'http%3A%2F%2Flocalhost%3A39783%2Fapi%2Fmessages'%20%7D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20console%20running%20the%20echo-skill-bot%2C%20I%20can%20see%20the%20activity%20from%20the%20simple-root-bot%20got%20passed%20but%20it's%20throwing%20the%20following%20errors%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%20%5BonTurnError%5D%20unhandled%20error%3A%20Error%3A%20%2Fapi%2Fmessages%2Fapi%2Fskills%2Fv3%2Fconversations%2Feb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%257Clivechat-emulator-skillconvo%2Factivities%2F00751950-966c-11ea-9f88-838c9883d7bc%20does%20not%20exist%0A%0A%20%5BonTurnError%5D%20Exception%20caught%20in%20sendErrorMessage%3A%20Error%3A%20%2Fapi%2Fmessages%2Fapi%2Fskills%2Fv3%2Fconversations%2Feb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%257Clivechat-emulator-skillconvo%2Factivities%2F00751950-966c-11ea-9f88-838c9883d7bc%20does%20not%20exist%0A%0A%20%5BonTurnError%5D%20Exception%20caught%20in%20sendEoCToParent%3A%20Error%3A%20%2Fapi%2Fmessages%2Fapi%2Fskills%2Fv3%2Fconversations%2Feb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%257Clivechat-emulator-skillconvo%2Factivities%2F00751950-966c-11ea-9f88-838c9883d7bc%20does%20not%20exist%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BIf%20the%20echo-skill-bot%20is%20trying%20to%20post%20a%20response%20to%20the%20simple-root-bot%2C%20then%20the%20conversation%20Id%20in%20the%20url%20should%20have%20been%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3Efc9260e0-966b-11ea-9510-8344e3862407%7Clivechat%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Einstead%20of%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3Eeb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%257Clivechat-emulator-skillconvo%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhere%20is%20the%20echo-skill-bot%20getting%20the%20conversation%20Id%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1398153%22%20slang%3D%22en-US%22%3ERe%3A%20Skills%3A%20Simple%20Bot%20to%20Bot%20and%20Skills%20Dialog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1398153%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20different%20tech%20versions%20for%20the%20Skills%20Simple%20Bot%20to%20Bot%20samples.%20Since%20I%20am%20having%20issues%20with%20the%20NodeJS%20version%2C%20I%20wanted%20to%20try%20out%20the%20DotNet%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELo%20and%20behold%2C%20the%20CSharp%20version%20of%20the%20Simple%20Bot%20to%20Bot%20sample%20actually%20works!%20The%20root%20bot%20can%20send%20activities%20to%20the%20skill%20bot%20and%20the%20skill%20bot%20responds%20beautifully.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22voonsionglum_2-1589772187183.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F192419i759A9F9A23AB5E82%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22voonsionglum_2-1589772187183.png%22%20alt%3D%22voonsionglum_2-1589772187183.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20that%20we%20know%20the%20CSharp%20version%20of%20the%20sample%20works%2C%20I%20wanted%20to%20know%20if%20the%20NodeJS%20version%20is%20breaking%20on%20the%20skill%20bot%20end%20or%20the%20root%20bot%20end.%20I%20replaced%20the%20Skill%20Bot%20App%20Id%20in%20the%20root%20bot%20with%20the%20NodeJS%20version%20and%20redeployed%20the%20root%20bot.%20It%20turns%20out%20that%20this%20scenario%20is%20also%20working%20correctly!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22voonsionglum_1-1589772013715.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F192418i5AE3DEE6291FC843%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22voonsionglum_1-1589772013715.png%22%20alt%3D%22voonsionglum_1-1589772013715.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20implies%20that%20the%20NodeJS%20version%20of%20the%20root%20bot%20is%20breaking.%20I%20went%20and%20updated%20the%20root%20bot%20NodeJS%20version's%20skill%20end%20point%20to%20the%20CSharp%20version%20of%20the%20skill%20bot.%20The%20NodeJS%20root%20bot%20never%20got%20a%20response%20from%20the%20CSharp%20version%20of%20the%20skill%20bot.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20feels%20like%20the%20NodeJS%20version%20of%20the%20SkillClient%20might%20be%20buggy.%26nbsp%3B%20Has%20someone%20else%20come%20across%20this%3F%26nbsp%3B%20Maybe%20I%20should%20open%20an%20issue%20in%20GitHub%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1476601%22%20slang%3D%22en-US%22%3ERe%3A%20Skills%3A%20Simple%20Bot%20to%20Bot%20and%20Skills%20Dialog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1476601%22%20slang%3D%22en-US%22%3ELooks%20like%20it%20had%20something%20to%20do%20with%20the%20bot-xxx%20NPM%20packages%20that%20I%20was%20using.%20After%20I%20updated%20to%20~4.9.0%2C%20I%20no%20longer%20have%20any%20issues.%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi,

We came across the Bot Service's Skills concept at https://docs.microsoft.com/en-us/azure/bot-service/skill-implement-skill?view=azure-bot-service-4.0&....  We cloned the Bot Samples and tried running both the Simple Bot to Bot and SkillsDialog samples.  Both are giving us the following errors

[onTurnError] Exception caught in sendErrorMessage: Error: /api/messages/v3/conversations/d24ed016-6872-4a57-bd99-c93aa061e32c-8b8cc16a-597d-4bae-a4e0-b992af4d9b38-a:11XpYDC7setK3n4POxpFnsvU_143zXeMzsTqFuspVzDeE5fmF02wN0tqvWdvSjd89cdG9f7RWm-Gr76RV8z-Ny3j4NM24noCOmWV7zUxqqBbyc6SILj8Fkz0iW2l2HYHN-msteams-skillconvo/activities/1589352227371 does not exist

 [onTurnError] Exception caught in sendEoCToParent: Error: /api/messages/v3/conversations/d24ed016-6872-4a57-bd99-c93aa061e32c-8b8cc16a-597d-4bae-a4e0-b992af4d9b38-a:11XpYDC7setK3n4POxpFnsvU_143zXeMzsTqFuspVzDeE5fmF02wN0tqvWdvSjd89cdG9f7RWm-Gr76RV8z-Ny3j4NM24noCOmWV7zUxqqBbyc6SILj8Fkz0iW2l2HYHN-msteams-skillconvo/activities/1589352227371 does not exist
It feels like the root bot/root dialog was able to send a Skill request/activity to the skill bot/skill dialog but the skill bot/skill dialog was not able to reply back to the conversation because the conversation could not be found.  Has anyone come across this?  How did you resolve this? 
 
Thank You
5 Replies
Highlighted

@voonsionglum , Did you implemented the conversation for skill? You can take a look at Implement the skill in Teams Skills Bot

Highlighted

@Trinetra-MSFT, thanks for responding.  The conversation for skill was implemented for the echo-skill-bot. 

 

When the root bot sends the skill activity to the echo-skill-bot, I can see that the latter did get the activity.  When the echo-skill-bot tries to send the reply to the root bot, it errors out saying that the conversation it tries to reply to does not exist.

 

I tried printing out the context when that error happens.  I can see that the conversation Id and the activity Id in the context match with the ones thrown by the error, but I don't know why the conversation does not exist.  It feels like something is missing...

Highlighted

Here is some more information.  I am running the simple-root-bot locally and opening it with the Bot Framework Emulator at port 3978.  I am running the echo-skill-bot locally at port 39783.  

 

In the Emulator, when I type in "skill", the simple-root-bot responds with "Got it, connecting you to the skill…".  I updated my rootBot.js so that before the "await this.sendToSkill(contextthis.targetSkill);" in the "onMessage" is called, I print out the context and the the target skill.  

 

The context shows the following conversation Id

 

 

 

conversation: { id: 'fc9260e0-966b-11ea-9510-8344e3862407|livechat' },

 

 

 

The targetSkill object has the following values

 

 

{ id: 'EchoSkillBot',
  appId: 'aaebe6ed-b0ee-4487-92b7-xxxxxxxxxxxx',
  skillEndpoint: 'http://localhost:39783/api/messages' }

 

 

On the console running the echo-skill-bot, I can see the activity from the simple-root-bot got passed but it's throwing the following errors

 

 

 [onTurnError] unhandled error: Error: /api/messages/api/skills/v3/conversations/eb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%7Clivechat-emulator-skillconvo/activities/00751950-966c-11ea-9f88-838c9883d7bc does not exist

 [onTurnError] Exception caught in sendErrorMessage: Error: /api/messages/api/skills/v3/conversations/eb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%7Clivechat-emulator-skillconvo/activities/00751950-966c-11ea-9f88-838c9883d7bc does not exist

 [onTurnError] Exception caught in sendEoCToParent: Error: /api/messages/api/skills/v3/conversations/eb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%7Clivechat-emulator-skillconvo/activities/00751950-966c-11ea-9f88-838c9883d7bc does not exist

 

 

 If the echo-skill-bot is trying to post a response to the simple-root-bot, then the conversation Id in the url should have been 

 

fc9260e0-966b-11ea-9510-8344e3862407|livechat

 

instead of

 

eb2e388f-58f1-4182-b04e-ad1d35244622-aaebe6ed-b0ee-4487-92b7-798c7ea17325-fc9260e0-966b-11ea-9510-8344e3862407%7Clivechat-emulator-skillconvo?

 

Where is the echo-skill-bot getting the conversation Id?

 

Highlighted

There are different tech versions for the Skills Simple Bot to Bot samples. Since I am having issues with the NodeJS version, I wanted to try out the DotNet version.

 

Lo and behold, the CSharp version of the Simple Bot to Bot sample actually works! The root bot can send activities to the skill bot and the skill bot responds beautifully.

 

voonsionglum_2-1589772187183.png

 

 

Now that we know the CSharp version of the sample works, I wanted to know if the NodeJS version is breaking on the skill bot end or the root bot end. I replaced the Skill Bot App Id in the root bot with the NodeJS version and redeployed the root bot. It turns out that this scenario is also working correctly!

 

voonsionglum_1-1589772013715.png

 

This implies that the NodeJS version of the root bot is breaking. I went and updated the root bot NodeJS version's skill end point to the CSharp version of the skill bot. The NodeJS root bot never got a response from the CSharp version of the skill bot.

 

It feels like the NodeJS version of the SkillClient might be buggy.  Has someone else come across this?  Maybe I should open an issue in GitHub?

 

Highlighted
Solution
Looks like it had something to do with the bot-xxx NPM packages that I was using. After I updated to ~4.9.0, I no longer have any issues.