Bug #3917
Updated by François ARMAND over 10 years ago
When Rudder automatically archives reports, it does it in 3 step:
# copy from ruddersysevents to archivedreports
# delete from ruddersysevents
# vaccumm
If the webapp is stopped between 1 and 2, we have the archive in an invalid state, causing it to fail later as it tries to insert already existing entries into the archivedruddersysevents.
In fact, we want to be able to have the archived execution reports on an other DB, so we don't want to add transaction, but be smart about how we handle already migrated reports.