polymarket_polygon.combo_actions table lists what happens to combos outside trading:
- splits and merges, which turn collateral into a Yes and No pair and back,
- redemptions, per user,
- the operations that build and reshape combos (wrap, compress, extract, inject, …).
combo_details as they were when the action was recorded. Splits and merges that happen inside a trade are not included. They are part of the fill and appear in combo_trades.
There is one row per action, unique on (block_month, tx_hash, evt_index).
market_id is the parent combo. On extract, inject, split_on_condition and merge_on_condition, the resulting or leftover combo is in related_condition_id and related_condition_id_2. To find every action involving combo X, filter WHERE contains(all_condition_ids, X).
Table Schema
Table sample
Query performance
combo_actions is partitioned by block_month. Always filter on block_time or block_month.
Example query
Previous version
Previous version (v1)
Previous version (v1)
Columns of the previous version, for queries that still use it. The migration guide maps each old column to its new name.