Forum Discussion
Problems with a project
That "works at 10, breaks at 12" pattern is a useful clue — it almost always means something was built around the number 10 specifically, not the cards themselves. Usual suspects:
- A trigger condition or variable comparison that hardcodes 10 (e.g., when cardCount = 10, show the results layer) and never got updated.
- The two new cards aren't fully wired — duplicated cards sometimes arrive missing a state, a trigger, or a layer reference the originals had.
Quick way to narrow it: test with 11 cards. If 11 works and 12 breaks, diff card 12 against card 10 trigger by trigger. If 11 breaks too, the count logic is the culprit.
And yes — attach the .story file to the thread if you can. Much faster than guessing.
Hey Mark
Thx for your reply 😊
I’ve tried various things, including adding one card at a time, but it makes no difference whether I have 11 or 12 cards—I’m still getting errors :( I’m convinced there’s a mistake in the True/False trigger, but I can’t find it.
So, if you’d be willing to take a look at it, I’d really appreciate it. I could send you the file I have, but can I send it too you
- AndrewBlemings-20 hours agoCommunity Member
You can attach it to a comment to get as many eyes on it as possible too. The screenshot below shows how.
- BallonBrian5 hours agoCommunity Member
Hi again..
I’ve attached the .story file here; if anyone can help me move forward, I’d be very grateful :) Originally, there were 10 cards, but I wanted 12, so I copied two of them—the ones labeled "prøve" in the last row.If anyone can spot the error, I’d certainly like to know what I did wrong so I can learn from it :)
Related Content
- 6 months ago
- 11 months ago