When creating a snapshot of a target system, the behavior differs depending on where the import fails: If the Account Entitlement import fails, an error is shown and the snapshot can be retried immediately. If the Permission Entitlement import fails, the snapshot cannot be retried immediately. Instead, a cooldown period of approximately one hour must pass before another attempt can be made. Why this is a problem During development, testing, and implementation projects, it is common for entitlement imports to fail due to configuration changes, mapping adjustments, or source system data issues. When a failure occurs during the Permission Entitlement import, the one-hour waiting period significantly slows down troubleshooting and validation efforts. After making a fix, administrators cannot immediately verify whether the issue has been resolved and must wait before the next test can be performed. As multiple test iterations are often required before a configuration is fully working, this results in unnecessary delays and reduced efficiency during both development and customer implementations. Suggested Improvement Allow administrators to manually retry a snapshot immediately after a Permission Entitlement import failure, similar to the current behavior for Account Entitlement import failures. This would: Reduce development and implementation time. Speed up troubleshooting and validation. Improve the overall experience when configuring and testing target systems. Remove unnecessary waiting time when resolving import-related issues. In short: if a snapshot fails during the Permission Entitlement import, administrators should be able to retry the snapshot immediately instead of waiting for the one-hour cooldown period.
