We have a bug in our caching logic that if a mod gets renamed/deleted/hidden on mod.io then the API endpoint will return 403/404 which prevents the cache from being updated, i.e. bricking mint. This is less than ideal, we should properly invalidate the relevant cache entries upon receiving such responses.

Current Workaround

• Remove deleted/renamed mod from profiles
• Delete the cache directory