Understand TranslateSense Database Caching
Understand the role of database-backed caching in translation processing.
TranslateSense stores translation memory in WordPress database tables. In version 0.0.8, caching is managed by the plugin; the inspected settings screen does not provide a cache-enable toggle, retention field, or documented manual purge control. You do not need to configure a separate database cache option to use the built-in translation reuse behavior.
What the database stores
Source strings: the original text, filtered text, a string hash, and creation time.
Translation packages: post and editor context, widget and field identifiers, language, package hash, and creation time.
Translation results: translated text linked to a string ID and target-language code, with creation and update timestamps.
The hash and package tables help TranslateSense find extracted content again. The translation result table is keyed by string ID and target language, so a saved translation can be reused when a later lookup matches. The persistent key does not identify the provider, model, or prompt.
Automatic cache maintenance
TranslateSense registers a daily WordPress cron event for cleanup. When that event runs, it deletes translation results whose updated_at timestamp is older than five days, deletes package records older than 30 days, and removes source-string records that are no longer referenced by packages along with translations whose source-string record no longer exists.
This describes the cleanup routine in the source. It does not confirm that cron ran successfully on your site or that all old data will disappear at an exact time. WordPress cron execution depends on site activity and configuration. See Check WordPress Cron for Translation Jobs if scheduled work appears delayed.
How to verify the behavior
Confirm that TranslateSense is active and that the translation workflow can extract the field you want to test.
Translate a short test phrase into a target language and review the output.
Repeat the same phrase to observe whether a saved result may be reused.
Change the phrase and compare the result; different source text may use a different hash.
Monitor database size and the WordPress cron status during normal maintenance. Do not infer cache health from one translation alone.
Can I clear the cache manually?The source contains an internal method that truncates the translation-results table, but no corresponding cache-clear setting was found in the inspected TranslateSense admin UI. Do not use database commands or call internal methods as routine troubleshooting unless you have a tested backup and a supported procedure for your exact build. Clearing translated results can cause future workflows to request translations again.
Related guides
Understand Translation Memory
Translation Memory and Database Caching
Check WordPress Cron for Translation Jobs
Understand Background Translation Processing
Screenshot to add: [Database cache tables and scheduled cleanup overview]
