Skip to content

Conversation

Copy link

Copilot AI commented Jan 29, 2026

Lab 3 instructs users to reference Amount Funded from the "Create new loan draw row" action for email body content. This field is never populated in that action, causing emails to display incomplete text ("Your draw for was approved" instead of "Your draw for 80000 was approved").

Changes

  • Lines 933-934, 957-958: Changed email body instructions to reference Amount Requested (set to 80000 in step 855) instead of Amount Funded
  • Added action name qualifier for clarity: "from the Create new loan draw row action"

Context

The flow creates a loan draw row with only Amount Requested set. The Amount Funded field is populated later by a child flow but not returned to the parent scope, making it unavailable for the email actions.

-1.  Type `Your draw for` in the Body and select **Amount Funded** from the
-    dynamic content pane.
+1.  Type `Your draw for` in the Body and select **Amount Requested** from the
+    **Create new loan draw row** action in the dynamic content pane.
Original prompt

This section details on the original issue you should resolve

<issue_title>Logical error in instructions</issue_title>
<issue_description>### Lab 3, Ex 4, Task 2, Step 71

User is instructed to use Amount Funded property from action Create new load draw row. This instruction results to email missing the Amount funded, because the value is not yet set in Create new loan draw row.

Image

Image</issue_description>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Fix logical error in instructions for loan draw row Fix Lab 3 Ex 4: Use Amount Requested instead of non-existent Amount Funded Jan 29, 2026
Copilot AI requested a review from skulthm-ms January 29, 2026 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logical error in instructions

2 participants