Trashed custom field in Production become Active in Sandbox after Data Copy from Production to Sandbox

Issue Summary

The customer is experiencing an unexpected behavior while refreshing their sandbox with production data, the custom fields are not being refreshed in the sandbox.

"when I viewed in Sandbox the custom fields, I found that there are still custom fields previously created in Sandbox that remained despite the refresh."

Steps to Reproduce

• Create a Sandbox
• Create a custom field in the production instance and Move it to the trash
• Copy data from production to sandbox
• Then, the custom field that was moved to the trash on the production instance will appear as active on the sandbox instance.

Expected Results

After the copy data from production, the sandbox should have the same data as the production instance, which means that if a custom field was moved to the trash in production it should appear as moved to the trash in the sandbox.

Actual Results

The custom field that was moved to the trash on the production instance appears as active on the sandbox instance.

Workaround

Permanently delete the trashed custom field in the production instance or even in the sandbox instance, if the copy from production was already done.