Error adding a skill created in Bot Framework Composer

(0) Share

Report

Posted on by craiglarrabee

I've created a skill using Bot Framework Composer 1.3.1.

When I add the skill in PVA, the skill validates, but when I Save it, I get the following message:

Something went wrong while importing your skill. Please try again later.
Diagnostic Trace Id:

Any help would be great!

Manifest:

{
 "$schema": "https://schemas.botframework.com/schemas/skills/v2.1/skill-manifest.json",
 "$id": "DynamicQuestion-6119ba95-166e-4296-8d87-f0858ac8f99a",
 "endpoints": [
 {
 "protocol": "BotFrameworkV3",
 "name": "DynamicQuestion",
 "endpointUrl": "https://my-skill-name.azurewebsites.net/api/messages/",
 "msAppId": "00000000-0000-0000-0000-000000000000"
 }
 ],
 "name": "DynamicQuestion",
 "version": "1.0",
 "publisherName": "Publisher",
 "activities": {
 "DynamicQuestion": {
 "type": "event",
 "name": "DynamicQuestion"
 },
 "conversationUpdate": {
 "type": "conversationUpdate"
 }
 }
}

Categories:

Bot extensibility

I have the same question (0)

All responses (3)

Answers (1)

Sort by

CU22081450-0 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @craiglarrabee ,

Are you trying to publish your Bot Framework Composer as a skill?

You need to follow this documentation here: Use Bot Framework Composer with chatbots - Power Virtual Agents | Microsoft Docs

Because when you are developing skills inside Bot Framework Composer, you need to publish inside the client and not inside the PVA

Was this reply helpful? Yes No
craiglarrabee 13 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the response @renatoromao .

I have been able to extend my PVA bot great with Composer Dialogs, however, I want the Composer Dialog to return me where I left in PVA, much like a Power Automate Action. I'm hoping skills will accomplish this.

I have successfully published the skill to Azure, and am trying to use it in PVA.

Thanks!

Was this reply helpful? Yes No
Verified answer

craiglarrabee 13 on at

Like
a
(0)

Report
Copy link

Link copied!

Just to close the loop...Several days later, after dealing with other fires, I came back to this, and it just worked. I still have no idea what was going wrong originally, but I'm past this issue.

Was this reply helpful? Yes No