Some conditions are loaded on the 1st event, so any timeouts from Frontier end up in the "other" messageCount (when it runs between 1st and last event.