Gasless relayer 500 on combo merge_positions (mints on same relayer are fine) Since 2026-06-23 ~19:25 UTC, every gasless combo merge returns HTTP 500 internal server error at POST /submit. The relayer is otherwise healthy — the same wallet + same relayer key submits mint/split txns continuously with a normal success rate. Nothing changed on our side, and it hits 100% of merge attempts including newly-created combos, so it's not position-specific. We already ruled out the client: diffed the latest SDK (polymarket-client 0.1.0b9) vs ours (0.1.0b7) — the combo merge path is identical (same router/module addresses, same selectors, same prepare_condition + merge bundle). Same request 500s regardless of SDK version → server-side. SDK: polymarket-client 0.1.0b7 (also repro'd as identical in 0.1.0b9) Relayer: https://relayer-v2.polymarket.com → POST /submit Chain: Polygon (137), deposit/proxy wallet (gasless) WORKS: mint/split via POST /submit — hundreds/hr, 0 errors FAILS: merge_positions(legs=..., amount="max") → 500 "internal server error", every attempt, every ~20 min since 19:25Z 06-23 Failing bundle: 1) combinatorial_prepare_condition → 0x30000034706c7d8e12009dab006be20000c031a8 2) merge (router merge selector) → 0x12121212006e4CD160D18e3f00711DA5c3372600 SDK reads on-chain balances first; amount resolves > 0 (both legs held on-chain, NOT a "no balance" case). Response body is literally "internal server error" — no request id / detail. Q: Known relayer-side regression on the combinatorial-merge path? ETA or workaround? Low urgency on our end (collateral self-recovers at resolution), but complete-set merges are fully blocked meanwhile. Can share a specific failing condition_id in DM to trace.
Gasless relayer 500 on combo merge_positions (mints on same relayer are fine) Since 2026-06-23 ~19:25 UTC, every gasless combo merge returns HTTP 500 internal server error at POST /submit. The relayer is otherwise healthy — the same wallet + same relayer key submits mint/split txns continuously with a normal success rate. Nothing changed on our side, and it hits 100% of merge attempts including newly-created combos, so it's not position-specific. We already ruled out the client: diffed the latest SDK (polymarket-client 0.1.0b9) vs ours (0.1.0b7) — the combo merge path is identical (same router/module addresses, same selectors, same prepare_condition + merge bundle). Same request 500s regardless of SDK version → server-side. SDK: polymarket-client 0.1.0b7 (also repro'd as identical in 0.1.0b9) Relayer: https://relayer-v2.polymarket.com → POST /submit Chain: Polygon (137), deposit/proxy wallet (gasless) WORKS: mint/split via POST /submit — hundreds/hr, 0 errors FAILS: merge_positions(legs=..., amount="max") → 500 "internal server error", every attempt, every ~20 min since 19:25Z 06-23 Failing bundle: 1) combinatorial_prepare_condition → 0x30000034706c7d8e12009dab006be20000c031a8 2) merge (router merge selector) → 0x12121212006e4CD160D18e3f00711DA5c3372600 SDK reads on-chain balances first; amount resolves > 0 (both legs held on-chain, NOT a "no balance" case). Response body is literally "internal server error" — no request id / detail. Q: Known relayer-side regression on the combinatorial-merge path? ETA or workaround? Low urgency on our end (collateral self-recovers at resolution), but complete-set merges are fully blocked meanwhile. Can share a specific failing condition_id in DM to trace.