Thank you for your response! After reviewing this discussion, I still have a few questions regarding the best approach to handle this issue: Do I need and how can I reliably detect that the widget is attempting to access Core Data during migration? What is the recommended way to prevent the widget from accessing Core Data until migration is complete? Does Apple provide any official mechanism to ensure that the widget does not interfere with Core Data migration? Is there a way to delay the widget's execution or data fetching until the migration is complete? Any guidance on best practices for handling this scenario would be greatly appreciated!