There are stored procedures in OO that clean up OO DB and keep data as needed, however the procedures do not look for some status, for instance cancel-timeout. Such data is not removed by the procedures.

The procedures do not look for status as a condition to determine completed versus uncompleted flows, rather look at end time. This decision is in place to avoid issues where flows have a completed status, but they are not yet finished (for example flows with nonblocking steps).

If these flows have manually been canceled, most likely that the end time long is null. This will disqualify the data from being purged.

If there are just a low number of executions with this issue users can correct them with the following query:
UPDATE OO_EXECUTION_SUMMARY SET END_TIME_LONG = START_TIME_LONG WHERE EXECUTION_ID = 'AFFECTED_EXECUTION_ID';

Then run the purge normally and it will clear the data for these flows as well. This is not a defect in the procedures, but it is a standard design.