Fix Ambiguous Pool Status

There were cases where multiple pool status events were emitted in the same block, which caused an ambiguous status to be reported. There was a quick fix in 78a00410 that was reverted since @huginntc has a related PR opened at !411 (merged). Once the event ids are populated please update the query to ensure the status from the last reported event is used.