Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

Commit

Permalink
Corrected the link to the Skill Invocation Flow (#1275)
Browse files Browse the repository at this point in the history
  • Loading branch information
arafattehsin authored and darrenj committed May 4, 2019
1 parent 07f03bd commit c0075bb
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/reference/skills/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ A key design goal for Skills was to maintain the consistent Activity protocol an

## Invocation Flow

![Skill Invocation Flow](/docs/media/virtualassistant-skillflow.png)
![Skill Invocation Flow](/docs/media/virtualassistant-SkillFlow.png)

### Dispatcher

Expand Down Expand Up @@ -73,4 +73,4 @@ The `SkillMiddleware` is used by each Skill and is configured automatically if y
The middleware consumes the `skill/begin` event and populates SkillContext on the Skill side making slots available.

## Interrupting Active Skills
Skills can be interrupted through a top-level interruption (e.g. "cancel"). The user is prompted to confirm before tearing down the active Skill. This requires each utterance, even during a SkillDialog to be inspected by the Bot Dispatcher to determine if cancellation is needed before then continuing. That is not shown in the above diagram for brevity reasons.
Skills can be interrupted through a top-level interruption (e.g. "cancel"). The user is prompted to confirm before tearing down the active Skill. This requires each utterance, even during a SkillDialog to be inspected by the Bot Dispatcher to determine if cancellation is needed before then continuing. That is not shown in the above diagram for brevity reasons.

0 comments on commit c0075bb

Please sign in to comment.