Event Counts, Discarded Chips & Retention

Here's what shipped in 26.7.4.

Events sent is the number of events

The 26.7.3 dashboard totals still counted Events sent from deliveries, and that number sat in cache for an hour. Successful and Failed moved with the live rollup. Events sent did not, so one event with two deliveries looked like two events sent.

It now counts event rows. The three cards stay on the same clock, and a fan-out no longer inflates the first one. Today's numbers can still sit up to a minute behind. After you upgrade, older event days fill in as Convoy walks back through your history.

Discarded is a skip, not a failure

A discarded delivery is a terminal skip. It used to share the red Failure chip. It now sits on a muted chip, the same family as Scheduled and Retry. Failure stays red.

The Events log route column says Matched when a subscription picked the event up, and Unmatched when none did. It no longer says Delivered for a match.

Retention follows the period you set

Changing CONVOY_RETENTION_POLICY after the first boot used to leave the stored window alone, so later drops kept using the old period. Convoy now rewrites that window when it registers the tables, and adopted-partition drops read the same row.

You still need a process restart, or the nightly job, after you change the period.

Index rebuilds wait out the daily counts job

The 26.7.3 rebuilds used one short timeout for both "is the table free?" and "are other transactions finished?". The minute rollup holds a transaction for tens of seconds, so a rebuild only succeeded in the gap between runs.

The table lock still has to clear in a few seconds. The build itself can wait for that rollup to finish. If it cannot, the error names the blocker instead of looking like a generic lock timeout.

Smaller fixes

• One event reads Event sent, one success reads Successful delivery, one failure reads Failed delivery
• The missing-number dash on the delivery cards, including the portal, is the same width as the dashes in the tables

Open Events and check that Events sent matches the events you ingested.