Spider2-Snow credential account suspended — same as #184, still blocking evaluation (2026-06)

[KyranFang]

Hi Spider2 team,

I'm running into the same suspension that was reported in #184 (still open). Just want to surface this is still happening 2+ months later, share some additional diagnostics, and ask what the recommended path forward is for current users.

Symptom

Using the credentials shipped with Spider2-Snow (account RSRSBDK-YDB67606, role PARTICIPANT):
Snowflake error 000666 (57014): Your account is suspended due to lack of payment method.

What I observed (might help with diagnosis)

The suspension is selective, not total — which suggests it's a warehouse-compute credit exhaustion rather than a full account block:

Query type	Result
SELECT 1	✅ works
SELECT COUNT(*) FROM <db>.<schema>.<table> (no filter)	✅ works (served from metadata, no warehouse)
SELECT COUNT_IF(<col> > N) FROM ...	❌ fails with above error
Anything with WHERE / GROUP BY / JOIN / FLATTEN	❌ fails

So the catalog is alive and reachable, but warehouse compute is blocked across every shared dataset (PATENTS, GITHUB_REPOS, TCGA_*, THELOOK_ECOMMERCE, ETHEREUM_BLOCKCHAIN, ...). This is consistent with the credit pool on the sponsored account being exhausted.

Questions

1. Could you confirm what's actually going on with the account — is it credit exhaustion, a billing/payment issue on the sponsored account, or something else?
2. Any rough ETA on a fix?

Happy to share the suspension log lines or the probe-script if useful for repro.

Thanks for maintaining Spider2 — the benchmark itself is great, just need to know how to keep evaluating against it.

[httdty]

+1