Ok so this is indeed an undocumented feature.
An updated version to resolve will be released in due course, however if you're currently impacted I suggest logging a case with support and they'll guide you through to truncate the data.
For us blowing away the FSDb wasn't an option as we need to be keeping 35days of history.