Conditions & Branching: "And" vs. Two Separate Ifs
Two conditions that must both be true are one decision, not two. Writing them as two IFs lets either one alone let something through.
The Conditions & Branching set has a challenge that requires two things to both be true before one outcome happens. The trap is writing that as two separate IF statements that each produce the outcome on their own, instead of one IF that checks both conditions together with AND. The two look similar enough to write by instinct -- they are not similar in what they let through.
Press Run to see what your code does.
isMember is true and hasCoupon is false, so this should show nothing -- the discount needs both. Instead it prints "Discount applied" once, because the first IF fired on its own and never checked the second condition at all. Combine them into one decision instead: IF isMember AND hasCoupon THEN. AND only lets the branch through when both sides are true, which is the actual rule the two separate IFs were trying and failing to express. If the real rule is "either one qualifies," OR is the right word -- the bug here specifically is using two IFs to mean AND when they behave like OR.
Everything above runs in this page, on your own machine. There is more of it on the practice pages.