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
Yes, unfortunately ITranslationJobLoadEventArgs does not fire for new job, so we do not have event for newly created job. This is our oversight and need to be added back to product.
But for now can you use Save event or is it changes that you do have to be added before user see job?
There is no problem in having in progress Translation Jobs during upgrade. They should work just fine.
But you need to remember to not run both old and new version of TM service simultaneously.
This of course happens when people instead of upgrade just install new version on other machine, while having old version still running. This can lead to ...
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 ...
Yes, mostly you did answer to your questions.
We did few migrations from SDL Tridion 2013 to SDL Tridion Sites 8.5 with Translation Manager, It worked fine for the in-progress items, I would recommend to having a change freeze during the final cutover DB refresh.
If your Translation Manager database is Cloud-based (AWS or Azure), it must use the ...
Tridion has an add-on product called Translation Manager that allows content to be sent to its own translation software (TMS, WorldServer, etc.) and then monitored and retrieved. Unfortunately, Translation Manager isn't compatible with other, non-SDL translation systems such as LionBridge.
However, Tridion is extensible and has the Core Service API for ...
Decision to not allow two WF processes comes from inability of CM to run two WF processes. It is also ambiguous how to orchestrate running one process after another since we do not know what need to be run when. If it need to run in same publication.
Original idea was to configure Translation Review process only in target publication.
You don't really need ...