Skip to main content

Why Some Combinations Aren't Allowed

Updated this week

If you've seen a message saying your picks can't be combined, here's what that means and how to fix it.

What is a correlated pair?

When you build a Same-Game Parlay (SGP), you're combining multiple picks from the same game into one entry. Some stat combinations are statistically linked β€” for example, a quarterback's passing yards and his receiver's receiving yards tend to move together. When the correlation between two picks is too strong, the combined multiplier exceeds what our system can fairly price, so the combination isn't supported.

The two ways this can appear

"These picks can't be combined. Remove one to keep building your entry."

You'll see this message while you're still building your entry, before you submit. Our system caught an unsupported combination on the fly. Nothing has been submitted β€” just remove one of the flagged picks and keep going.


​What to do: Remove one of the conflicting picks from your entry. You can still use either pick individually or pair them with other eligible stats.

"One or more picks couldn't be added."

You'll see this message as a notification after you tap Submit. This means your entry was reviewed at the time of submission and one or more pick combinations couldn't be priced or the market was unavailable at that moment.

What to do: Review your picks and check our rules for a full list of unsupported combinations. You may need to remove one or more picks before resubmitting.

Why does this happen?

We use two layers to catch correlated picks:

  • Built-in rules per sport (NFL, NBA, NHL, MLB, WNBA, and others) that flag known stat combinations before you submit.

  • Live pricing checks at submission that evaluate your full entry. If the combination can't be priced or the market has been suspended, the entry is rejected at that point.

Both layers are there to keep the game fair and competitive for everyone.


Still have questions?

If you believe your picks should be valid or you keep running into this error, reach out to our support team and we'll take a look.

Did this answer your question?