@diosmosis opened this Issue on July 11th 2021 Member

Sometimes both a plugin specific/report specific archive invalidation will exist alongside an all plugins archive invalidation. When processing these, the all plugins archive is processed first. Then the plugin specific/report specific ones are ignored, since we have a valid archive that was just created. This means those plugin/report specific invalidations never get deleted from the table.

So in this case, if there is a valid archive and the invalidation in question is plugin/report specific, we should just delete the invalidation instead.

Powered by GitHub Issue Mirror