Ensure Sidekiq queue is not lost when migrating an Organization

Problem statement

Org data migration does not move the Sidekiq job queue for an org.

Also, we have not start distinguishing jobs that would, or would not mutate an Organizations.

Most background jobs are OK to be lost / should eventually be re-queued. However, there could be some background jobs that should be run and are never re-queued.

Example: PostReceive

Options

  1. Isolate async jobs (#562973), and then make sure 100% of the Sidekiq job queue for that Org is drained
  2. Drain 100% of the Sidekiq job queue before migrating an Org

Something else ?

Edited by Thong Kuah