Skip to content

Removing local skills and then adding remote skills breaks Enterprise Assistant Template intents #8836

Open

Description

I am using the Enterprise Assistant template which includes the core bot, and the Calendar, People skills.

I first created and tested the bot successfully locally. I published all the skills and the core bot to Azure, and everything worked fine locally. However when testing externally the core bot couldn't connect to the skills properly because the skills were not configured to connect to the remote skills that I published to Azure.

Following this tutorial : https://docs.microsoft.com/en-us/composer/how-to-connect-to-a-skill?tabs=v2x

I deleted the local skills. The moment I did that I got errors in Composer on skills not being found (which I resolved by connecting remote skills), and warnings saying :

" line 55:0 - line 55:57 Orchestrator does not support ML entities. "

Despite adding remote skills to the root bot project and modifying the triggers to connect to the remote skills, Composer fails to detect any of the intent definitions. Trying to build the bot locally or publish results in an immediate error :

"[ERROR] line 105:0 - line 151:34: Features can only be added to intents that have a definition. Invalid feature definition found for intent GetDepartment"

I have not touched intents at all, all I did was follow the instructions. What am I doing wrong here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

BacklogBacklog items - not in current milestoneBot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.ExemptFromDailyDRIReportNeeds-triageA new issue that require triagecustomer-replied-toRequired for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions