Reset the cron queue

If I get this right, you're talking about queue items that have not been processed yet, but configuration is already changed?

I agree in that case, the queue should be cleared to be rebuild by next run. Or did I get something wrong here?

5 years later, is it still a problem?

FYI, as of now, when cron is run, if the queue is not empty, nothing is done, we wait for the next cron run.

The feature has been added in this issue's MR: ✨ Use plugins and condition to create advanced policies Active

It only works with the new policy configuration form for now.