It's assumed that tenant migrations happening with RRFaM turned on will omit the data in config.image_collection necessary to service a retried findAndModify.

It's also assumed that this state can be avoided by temporarily disabling RRFaM for the duration of the tenant migration.

For this ticket we aim to:

• Confirm that disabling RRFaM is sufficient to service retryable findAndModifies across a tenant migration
• Aim to do better and understand the code change necessary to make tenant migrations RRFaM aware.
• Understand the prioritization of when a code solution should be typed up.