Feature Request: One-Click Tool to Reset Imagify Internal State (Clear Transients and Stuck Jobs) #1012
Description
Context:
Optimization getting stuck is one of the most common technical issues in Imagify. While it can have multiple root causes (blocked connections, low memory, server limitations, etc.), in a large number of cases everything on the server side is actually fine.
Despite that, the UI continues to show issues such as:
• Endless optimization loading
• Optimization stuck at a certain percentage
• False “out of quota” error messages
In most of these cases, when we log in to the user’s site, the issue is resolved simply by deactivating and reactivating the plugin, or by reinstalling the plugin. After that, optimization starts working normally again.
This clearly indicates that the problem is often related to stale internal state, transients, or cached data rather than a real server or account issue.
Although we often have to log in to the user’s site to fix the issue, asking users as a first step to delete transients manually or to reinstall the plugin is not a great experience. These steps feel risky and uncomfortable for users and are not something we should rely on as a primary troubleshooting action.
Instead, we could provide a dedicated button, either directly inside the Imagify plugin or inside Imagify Tools (even if it requires a separate installation), that performs the same internal cleanup that happens when the plugin is deactivated or reinstalled.
This would be similar to tools used in page builders, such as “Regenerate CSS” or cache purge actions, where users can safely reset internal data without breaking anything.
This is one of the issues I already raised with Nicolas during the Retreat.
Based on the code behavior, this is what currently happens when the plugin is deactivated or uninstalled.
Ideally, this button should not delete user settings and should not require the user to go through the setup again. It should only reset internal data, transients, and job-related state needed for optimization to work correctly.
This button could serve as a simple and safe first troubleshooting step for users. It would help resolve many “optimization stuck” cases on its own and would significantly reduce the number of support tickets.
I am attaching a few examples (out of many) where reinstalling or reactivating the plugin resolved the issue.
https://secure.helpscout.net/conversation/3104976053/591955
https://secure.helpscout.net/conversation/3196531155/614656
https://secure.helpscout.net/conversation/3103713746/591646
https://secure.helpscout.net/conversation/3103140053/591550
Additional Information:
In a few cases where everything looks fine at the server level and even reinstalling the plugin does not help, there is one more workaround that has helped users resolve the issue.
As a last step, we sometimes ask users to delete the imagify_optimize_media_batch rows from the wp_options table in the database. After doing this, optimization starts working again.
I am not fully sure whether this behavior is already tied to any existing uninstall or deactivation logic, or if this is a completely separate case that only affects the database state. The recurrence of this issue is not as regular as the other “optimization stuck” cases, but it does happen occasionally.
If this is related and technically safe, it might be worth considering whether this cleanup can also be handled by the same one-click troubleshooting button. That said, this would need careful validation to avoid any unintended side effects.
Attaching a few recent tickets where this workaround helped resolve the issue.
https://secure.helpscout.net/conversation/3131592480/598132
https://secure.helpscout.net/conversation/3112646772/593564
https://secure.helpscout.net/conversation/3192961069/613492
https://secure.helpscout.net/conversation/3135232978/599003