Hi! @Jon and team,
I’m working through the Level 1 course and running into a grading issue that’s happening consistently across two separate exercises in the same course, so I don’t think it’s a one-off mistake on my end.
My Assessment ID: 3f2695aab2f5175f5c7499185abc0479
Exercise 1 — CalculateBookedProcessingOrders node (Questions 5 & 6):
Code (copied exactly from the docs):
javascript
let items = $input.all();
let totalBooked = items.length;
let bookedSum = 0;
for (let i=0; i < items.length; i++) {
bookedSum = bookedSum + items[i].json.orderPrice;
}
return [{ json: {totalBooked, bookedSum} }];
Node output: totalBooked: 14, bookedSum: 1393.61
I submitted these exact values (copied directly from the JSON output view, not the rounded Table view) and both were marked incorrect on the first attempts.
Exercise 2 — CalculateBookedOrders node (Questions 7 & 8):
Same logic, different node in the workflow. Output: totalBooked: 16, bookedSum: 2251.14
Submitted these exact values as well — also marked incorrect.
Why I believe this is a grading bug rather than my error:
- The code is identical to the official documentation example in both cases.
- I double-checked the raw JSON output (not the Table view) to rule out floating-point rounding issues — no trailing decimals, values are exactly as submitted.
- The dataset appears stable across multiple executions (I get the same totalBooked/bookedSum values consistently when re-running the workflow), so this doesn’t look like a data-randomization issue.
- This is happening on two different questions/nodes with the same pattern, which suggests something systemic in how the answers are being checked rather than an isolated mistake.
Could someone take a look at my Assessment ID and see if there’s a mismatch between what the workflow generates and what the grading system expects? Happy to share screenshots of the node configs and outputs if that helps.
Thanks for your time!
