If you’ve upgraded to Mautic 7 and noticed that the cache:clear command runs lightning-fast — almost too fast — with zero output or success message, you’re not imagining things. A user recently flagged this on the community forum, asking if the cache is actually getting cleared or if something’s amiss compared to the old Mautic 6 behavior where the system confirmed the action.
That said, the quiet nature understandably raises eyebrows, especially if you’re used to the old feedback loop. The community hasn’t reported any bugs or missing functionality tied to this change, and Mautic’s GitHub issues currently don’t flag this behavior as a problem—looks like it’s by design rather than a bug.
Here’s the takeaway for your day-to-day Mautic use: Don’t sweat the lack of confirmation messages anymore. If you want to verify cache clearing after running the command, a quick way is to check timestamps or changes in your cached files or just rely on Mautic’s normal functioning—if caches weren’t clearing, you’d see wider symptoms, like stale content or broken workflows. In practice, everything is working smoothly.
If you want to weigh in or see how others are handling this, definitely peek at the original forum thread. It’s a neat peek into how even small UX changes ripple through the community.
Join the discussion here on the Mautic forum and share your experience.
