You can try the below events related to Workflow:
1.Event for Workflow process starts
EventSystem.Subscribe<ProcessInstance, StartWorkflowEventArgs>(OnProcessInstanceStart, EventPhases.Initiated);
2.Event for Workflow activity starts
EventSystem.Subscribe<ActivityInstance, StartActivityEventArgs>(OnActivityInstanceStart, EventPhases....
Looks like you may be using the wrong event? I don't know which event it is neither, so what I'd probably do is write a small event system that triggers on every event and logs enough details for me to be able to identify the one triggered by translation manager.
Something along the lines of this Example on Github
For the translation source and target Publications to properly match, they must have matching configuration (same Project Type and Clients for WorldServer).
See the Translation Manager resolving logic, and specifically how push and pull translations work.
Note that a SDL WorldServer configuration specifies the Client and Project Type that specifies the ...
Yes, if configured, Metadata fields are sent to translation out-of-the-box.
Per the Documentation:
You can control which Text fields and External Link fields are sent for translation in Schemas by selecting the Translatable check box in:
Embeddable Schema fields
Schema metadata fields
Multimedia Schema metadata fields
This limited mostly by how big of a request TMS API can handle.
Translation Manager send all files in one request so if it is not split, at some point TMS API will fail with timeout or something.
Another consideration, is that with big amount of tasks in one job, TMS UI can become unwieldy for people who work on TMS side.
Also, if customer uses out-scaled ...