@loparev,
We still run into these issues today. Correct responses are received, with content like this:
[processUid] => 3107a0c4-954d-4db5-ac48-ae07f0e8f598
[processState] => IN_PROGRESS
[processType] => MATCH_CONTEXT
[createdDate] => 2025-09-10T14:10:46Z
[modifiedDate] => 2025-09-10T14:10:46Z
[result] => Array ...
Until it switches to state COMPLETED, so the functionality works as designed but it sometimes just takes to long. We tried increasing the time-out to 30 seconds, but it still happens to often. I'll try to capture some of the problematic process ID if you can use those the check logs or something?
Is it really necessary to wait for the matching to complete processing? Edit: If I read the code correctly the response is only used to log a message? I assume it's enough to wait for the upload to complete and continue on Drupal's side?
From time to time queue items are building up rapidly because a lot of translations are being requested (campaign season for our client). We already disabled cron processing to not disturb other processes. See https://www.drupal.org/project/tmgmt_smartling/issues/3545995