As if the low volume of jobs was not a sufficient issue, 2 weeks ago I alerted Gengo support about a new "funny" bug which has not been fixed till now.
All the preferred collections of the EN>FR-CA language pair which appear on my dashboard remain out of my reach and generate an error message never seen before. My dashboard may show a dozen of jobs but it is impossible for me to take any of them, not because they are already taken by another translator but because (according to the error message), I am not in the preferred list of these clients. But then, they remain for hours on the dashboard...where they shouldn't be in the first place if the error message tells the truth!!
Note: my main language pair remains unaffected (EN>FR). The issue impacts only the EN>FR-CA pair.
So, as all the jobs are mixed on the dashboard (the ones I can try to take (EN>FR), and the ones (EN>FR-CA) which are labelled as "not for you, sorry"), it requires more time to find the "clickable" ones in the list. And we all know what this lack of reactivity means for us...
Very confusing bug.
I was told that other translators are experiencing the same issue. And so, 2 weeks later, the issue is not fixed yet? This is how LionBridge cares about the freelance translators? Should we consider that Gengo is now a kind of jungle with no rules and no respect?
PS: I've just noticed that Claudius wrote a post about this issue some days ago...
To give a bit of feedback, I just had the bug one minute ago in the EN/FR pair too. Mini-job, so nevermind. It is not solved as of today. I understand this is frustrating for you. I try my best to ignore the bug and not let these little inconveniences and bunches of 0010001111 binary codes ruin my days. Hit the gym, see the flowers in gardens, and so on. Have a nice day.
There is nothing that can spoil my days... That doesn't mean I should remain silent when something that worked well in the past is now a mess. Because that's what Gengo has become. If nobody says anything, then nothing will be done.
And 6 days after this message (so 3 weeks after my email to Gengo support), the problem is still the same!
Did you notice most of the jobs we can't access since we are not "preferred translators" are not exactly worth a few cents? (There are days I see more work in dollars worth I can't access, than jobs I can work on. Which has never been the case before, and I may not be the only one to have witnessed this. But nevermind...)
The situation reminds me of what happened to creator contents when YouTube decided to change their algorithm without communicating with them, a while back. All the odd things many translators noticed can be related to a deeper change decided by Lionbridge. Gengo was doing great, but since the company was purchased, a lot has changed: MT jobs appeared, allowing lower pays for workers (as we know Lionbridge is obviously very interested by IA), now our work tool has been messy (not to say confiscated) for several months without much action or communication about what they are implementing right now. What I mean here, from the facts I observe, is that no honest communication from company officials can only lead to an increasing amount of speculations from the workers based on the clues they can catch between the RSS and the dashboard, and what's going on in the translation industry outside of Gengo. Next on the theory line will be the "accomplice theory" between Lionbridge and the hackers/job-siphining system, as I read earlier today, and so on, which may hurt company's reputation. This is just my analysis, but if Lionbridge wants to change the rules of the game and abolish the "first come first served" or switch to a full-IA system they may be testing now, or whatever they want to do from now on: at least, state it clearly. I hope this message will reach the right persons.
Sometimes, things are so absurd it feels like El0n Musk is our new CEO.
Great comment Claudius, specifically the conclusion! :) Yes, the acquisition by LionBridge is the issue.
Hi @logos! Thanks for sharing this. I apologize for the late response.
This "preferred translator issue" bug is still in the investigation process. Our community manager, Maria, personally asked for an update about this issue, and we hope to resolve this bug soon. If you are still experiencing this issue, I would appreciate it if you could send me more details or screenshots. You can send it to v-Rica.Tero@lionbridge.com.
@Claudius- Thanks for sharing your input on this thread. I will relay this to Maria and Gosia. 😊
We got an update from the dev team that the issue is now resolved. If you still have any issues with it, don't hesitate to message me directly at v-Rica.Tero@lionbridge.com so I can immediately relay this to the team. Thank you for your patience and understanding in this matter.