Repository navigation
Inventory Planning Fabric: make Challenge 5 workflow easy to follow and complete - #611
Merged
Marco Weber (qxsch) merged 4 commits intoNov 10, 2026
Conversation
…nd complete - Build from the Sequential template; no manual data wiring between nodes (shared conversation) - Approval gate: create the LatestMessage variable the loop condition relies on (previously missing) - Pre-flight check, per-part checkpoints, Save-after-every-change warning - Troubleshooting for the failures teams hit; optional extras moved below success criteria - Walkthrough updated with the finished-node table and coaching tips Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ter 1 December 2026 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Verified end to end on a fresh lab (9 Nov 2026): delete template notes, add End node, keep the default Input message Local.LatestMessage, save once valid, refresh before Preview. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…live run Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Digvijay (Digvijay)
pushed a commit
to Digvijay/MicroHack
that referenced
this pull request
Nov 12, 2026
Resolve conflicts with microsoft#611: keep the hosted-assistant challenge and walkthrough, move microsoft#611's live-verified visual-workflow steps, screenshots and troubleshooting into archive/visual-workflow-exercise.md, and drop the now-unused challenge-04-orchestrator.png. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes Challenge 5 (Orchestrate the Loop, stretch) of Inventory Planning Fabric easy to follow and complete for the 18 November 2026 delivery (Finland). Coaches reported that teams couldn't finish the last challenge.
Likely root cause
The approval-gate Loop condition reads
Local.LatestMessage, but no step told teams to create that variable. Step 4 instead suggested other output names (demandAssessment,reorderTable). Followed literally, this gives a "Name isn't valid" error or a run that never waits for approval.Changes
System.ConversationId), so each agent already sees the previous reply. The Save output as / Input message step is removed.replenishment-action-agentnode: multi-turn on, Save agent output message as → new variableLatestMessage, and the copy-paste loop condition explained in plain words.Verified
submitted to ERP/Order cancelledmatch the Challenge 4 instructions exactly (case-sensitive).data/products.parquet: P004 $95, P005 $140, P006 $85.Not yet done: a live portal run on a fresh lab. Coaches will re-test before 18 November.
Relation to #584
Draft #584 replaces this visual-workflow challenge with a hosted Agent Framework assistant after the 1 December retirement. It touches the same two files, so on rebase keep #584's versions.