It's so annoying. Missions don't complete, markers are not shown, critical items don't even show up. I'v rarely seen anything else that was similarly frustrating.
While I think, it's mostly backend issues with servers losing track, connection or anything in the middle, it's super frustrating to waste time with this.
Especially given, that some of these missions take forever to run. Load 230 small boxes into your ship by hand just to arrive at the destination, noticing that one of them is missing. No partial fulfillment, just rinse and repeat.
They really need to focus on thheir background services!
I spent two weeks fixing a release blocker and got a quiet thumbs-up. Someone repeated my status in a meeting and got called strategic. At this point people joke about it before planning even starts, which says everything. I tested every workaround people suggested and none of them solved the root issue. It drains energy because you have to babysit something that should just work. One clear timeline and one accountable team would remove most of this pain.
I did five rounds, a case study, and a panel. The role was reposted anyway, just with a slightly different title. Everyone can see the pattern, but the same cycle repeats because no one really owns the fix. I even compared with similar services and this one still handles it worse. The issue compounds quietly until normal tasks feel heavier than they should. The fix is not complicated: keep context, name an owner, and stop forcing restarts.
They want strategy, analytics, execution, design, and support ownership, then offer mid-level pay like this is a normal request. This is not a one-off in my team, it is basically the default mode every quarter. I tried the documented path exactly as written, but each handoff reset the conversation. After a few weeks it becomes less about one incident and more about constant background friction. No full redesign needed, just stable basics and honest status updates.
My calendar is full of updates all day, then everyone wonders why actual output happens after dinner. This is not a one-off in my team, it is basically the default mode every quarter. I used the official route, logged everything, followed up twice, and still ended up back at step one. What this really burns is time, attention, and trust in the system. If effort-to-resolution were measured honestly, this would move up the priority list fast.
Some companies hand out tasks big enough to fill a sprint and call it screening, then send a generic rejection with no feedback. Everyone can see the pattern, but the same cycle repeats because no one really owns the fix. I tried the documented path exactly as written, but each handoff reset the conversation. After a few weeks it becomes less about one incident and more about constant background friction. No full redesign needed, just stable basics and honest status updates.
We get told to focus, then leadership flips direction in the final week and acts surprised when quality drops. At this point people joke about it before planning even starts, which says everything. I used the official route, logged everything, followed up twice, and still ended up back at step one. What this really burns is time, attention, and trust in the system. If effort-to-resolution were measured honestly, this would move up the priority list fast.
Exact matches keep getting pushed down while promoted noise takes the top slots. The app looks polished, but everyday actions somehow keep getting slower. I tested every workaround people suggested and none of them solved the root issue. It drains energy because you have to babysit something that should just work. One clear timeline and one accountable team would remove most of this pain.
Code accepted. New password set. Then it throws me back to step one like nothing happened. The app looks polished, but everyday actions somehow keep getting slower. I tested every workaround people suggested and none of them solved the root issue. It drains energy because you have to babysit something that should just work. One clear timeline and one accountable team would remove most of this pain.
That is not a reminder. That is a receipt pretending to be communication. Each handoff feels like starting from zero with a new person reading from a script. I used the official route, logged everything, followed up twice, and still ended up back at step one. What this really burns is time, attention, and trust in the system. If effort-to-resolution were measured honestly, this would move up the priority list fast.
People with years of proven results still get treated like strangers applying from outside. Trust feels performative. At this point people joke about it before planning even starts, which says everything. I tested every workaround people suggested and none of them solved the root issue. It drains energy because you have to babysit something that should just work. One clear timeline and one accountable team would remove most of this pain.
The loudest update wins. Quiet, high-impact work gets buried unless someone with influence repeats it. This is not a one-off in my team, it is basically the default mode every quarter. I even compared with similar services and this one still handles it worse. The issue compounds quietly until normal tasks feel heavier than they should. The fix is not complicated: keep context, name an owner, and stop forcing restarts.
