Problem: After migrating a fully translated site from local to live, the client could not create new translation jobs due to an error stating 'translator could not be assigned to the job'. Despite confirming that REST API and admin-ajax were functional, and even after redoing the migration and attempting ATE sync troubleshooting, the issue persisted. Solution: We discovered that the structure of WPML's translation status table was altered during the migration. We corrected this issue, and now the translation jobs should function correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please do not hesitate to open a new support ticket at WPML support forum.
