Database Deadlock in TranslatePress Machine Translation

  • Resolved fajarsusilowati83

    (@fajarsusilowati83)


    1 day, 3 hours ago

    Hi TranslatePress Support,

    I noticed a WordPress database deadlock error while using TranslatePress on my website.

    The error occurred while I was working with translations and appears to originate from TranslatePress machine translation:

    WordPress database error Deadlock found when trying to get lock; try restarting transaction

    The affected query was an INSERT IGNORE into:

    wp_trp_machine_translation_locks

    The error trace includes:

    TRP_Machine_Translator->translate
    TRP_Machine_Translator->claim_strings_for_machine_translation
    TRP_Query->claim_machine_translation_locks

    The request was made through:

    wp-admin/admin-ajax.php

    I have also noticed another issue around the same period where the Forminator form editor displays a blank white page. I have tested Forminator with TranslatePress disabled using WordPress Troubleshooting Mode, and the Forminator editor still remains blank, so I am not sure whether the two issues are related.

    The front-end translations and forms are currently still working.

    My environment:

    • Hosting: WordPress.com
    • WordPress: 7.1.2
    • PHP: 8.4.26
    • TranslatePress: Free version
    • Forminator: 1.57.3

    Could you please advise whether this database deadlock is a known issue with TranslatePress machine translation and whether any action is required to prevent it from recurring?

    I would prefer not to modify or delete the translation database tables because this is a live research assessment website.

    Thank you for your help.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Daniel

    (@danieldandu)

    23 hours, 41 minutes ago

    Hello @fajarsusilowati83

    Thank you for reaching out.

    Could you please help us investigate this further by sharing a couple of screenshots?

    Please go to WordPress Dashboard > Plugins > Installed Plugins and send a screenshot with everything you have installed related to TranslatePress.

    Go to Settings > TranslatePress > Advanced > Debug tab and you’ll see the option “Here you can observe the last 5 SQL errors relevant to TranslatePress if they exist.” Click on the “Here” link to view any SQL errors. If you do see any, please send me a screenshot of that section so I can review them.

    You can use a free tool like snipboard.io to upload and share the screenshots.

    Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    23 hours, 12 minutes ago

    Hi Daniel,

    Thank you for your response.

    I followed the steps you suggested. When I go to Settings > TranslatePress > Advanced > Debug and click the “Here” link for the last 5 SQL errors, it takes me to the TranslatePress Errors page. However, no individual SQL errors or timestamps are displayed there. I have included a screenshot showing exactly what I see.

    I have also included a screenshot of the installed plugins related to TranslatePress, as requested.

    TranslatePress plugins:
    [paste Snipboard link]

    TranslatePress Errors page:
    [paste Snipboard link]

    Please let me know if there is another location where I can retrieve the SQL error details.

    Thank you.

    Plugin Support Daniel

    (@danieldandu)

    18 hours, 21 minutes ago

    Hello @fajarsusilowati83

    Thank you for sending the screenshots.

    The TranslatePress Errors page does not capture every database error, so an empty list does not rule out the deadlock you reported.

    The wp_trp_machine_translation_locks table contains temporary locks used to prevent simultaneous requests from translating the same text more than once.

    The reported error relates to these locks and, by itself, does not indicate that your saved translations are damaged. There is no need to delete or modify your translation tables based on this error.

    To investigate further, could you please provide:

    • Whether the error occurred only once or continues to appear.
    • The original error entry, including the timestamp and full query/trace

    Since your site is hosted on WordPress.com, you can also check their site logs: https://wordpress.com/support/site-logs/. If you cannot access the relevant entries, please ask WordPress.com support to retrieve the database error details from around the time the issue occurred.

    At this point, we do not have enough information to determine whether this was an isolated concurrency issue or a recurring problem that requires further investigation.

    Since your front-end translations are working correctly, monitoring the site for additional occurrences is a reasonable next step.

    Regarding Forminator, the fact that the editor remains blank even with TranslatePress disabled suggests that this is a separate issue. Please share this troubleshooting result with Forminator support, along with any errors logged when opening the editor.

    Thank you!

    Thread Starter fajarsusilowati83

    (@fajarsusilowati83)

    18 hours, 6 minutes ago

    Hi Daniel,

    Thank you. I checked the WordPress.com Site Logs and found that the deadlock occurred at least twice on 29 September 2026, rather than only once.

    The first occurrence was shown in the WordPress.com log at 10:55 AM (Europe/London). The query timestamp was 2026-09-29 09:55:32. This occurred during an UPDATE of the wp_trp_machine_translation_locks table.

    The second occurrence was shown at 10:34 PM (Europe/London). The query timestamp was 2026-09-29 21:34:18. This occurred during an INSERT IGNORE INTO the same wp_trp_machine_translation_locks table.

    Both entries have the same relevant trace:

    TRP_Editor_Api_Regular_Strings->get_translations
    TRP_Editor_Api_Regular_Strings->get_translation_for_strings
    TRP_Translation_Render->process_strings
    TRP_Machine_Translator->translate
    TRP_Machine_Translator->claim_strings_for_machine_translation
    TRP_Query->claim_machine_translation_locks

    I have copied the complete original query and trace for both occurrences from the WordPress.com Site Logs. I can provide the full entries if required.

    The front-end translations are currently still working correctly, and I have not noticed any loss of saved translations.

    I will continue monitoring the Site Logs for any further occurrences.

    Thank you also for confirming that the Forminator editor issue appears to be separate.

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.