As far as i understand it , when a configuration is saved and the cron been selected, the queue db table is filled with tasks.
When changing configuration, the queue db table is not reset.
That means that if a mistake has been done initially while configuring, users and contents could be deleted by error in a radical way.
solution:
Reset the db queue table on each configuration saving
Active
4.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
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?