Introduction
You might encounter a situation where the option to view the "Run Report" or the "Dry Run" results is grayed out and unclickable in the JFrog Platform UI.
This article will guide you through the primary troubleshooting steps to understand why the report is unavailable.
Resolution
When a Cleanup Policy report is unavailable, it could be caused by two main scenarios: the job encountered an error during execution, or the job ran successfully but found absolutely nothing to clean up.
Step-by-Step Instructions
1. Check for Execution Errors in the Logs If a policy fails to execute properly or finishes in a state like Failed/Completing with Errors, the system may not generate a valid report to display.
- Action: Access your Artifactory server and review the artifactory-service.log file.
- Search for the specific Cleanup Policy name or look for timestamps correlating with the scheduled run.
- Investigate any WARN or ERROR messages indicating that the cleanup job failed to complete.
2. Verify if Any Packages Matched the Condition If there are no errors in the artifactory-service.log, the most likely explanation is that the policy executed perfectly, but no packages matched your defined conditions. If zero artifacts are flagged for deletion, there is no data to populate a report, resulting in the button being grayed out or inactive.
3. Double-Check the Policy Conditions To resolve the issue of no matching packages, you must review the exact criteria you set for the Cleanup Policy.
- Navigate to your Cleanup Policy settings in the UI.
- Carefully review the time-based criteria (e.g., "Delete artifacts older than X days").
- Verify the include/exclude patterns and ensure you are targeting the correct package types and repositories.
- Reference: For detailed guidance on configuring these conditions correctly, please review the official documentation on Creating a Cleanup Policy for Packages.
Conclusion
By first checking the artifactory-service.log for hidden errors and then verifying that your policy conditions are actually capturing the intended artifacts, you can quickly identify why a Cleanup Policy report is grayed out. If the policy is simply not finding matching artifacts, adjusting your timeframes or path filters will usually resolve the issue and generate a report on the next run.