TFs getting bugged when someone quits?

This happened twice to me in the last week, both with WST TF runs.

Run 1: Numina's last Sunday, I started a team, we got to the CoT map in Perez (just before the zone-hunts) and someone quit the TF. We finish the mission (find Envoy, clear the room), everyone exits, I try to call it in but the mission has reset. We find & clear Envoy's room again, everyone exits, and the mission resets again. After a bit of discussion, we quit. Some on the team mention they've seen this before, but it was the first time for me.

Run 2: ITF last night. Someone else started the team, then passed me the star. 2nd mish (cyst hunt) and someone quits. Coincidentally (or is it?), it's the same exact guy who quit (I've since 1 starred him, since he was lying about why he quit, but that's irrelevant), and when we exited the mish after completion, I couldn't talk to my contact and the mish had reset. Again, we quit and started over, and I did all the re-inviting. Now, on this new run, we had yet another guy quit on the 3rd mish, but we still were able to successfully complete it, and the TF as a whole.

/bugged the incidents, but did not /petition, because no one wanted to wait around for a response. Anyone else experience similar problems?

I believe this issue used to be in the /gmotd, but I'm not sure it was ever resolved. (Apparently not, since you still encountered it).

In my personal experience*, this only happened to me when there was a change in leadership before the TF began. For example: "Pass star to me so I can invite my friend". In some cases, if that former leader is the one that drops off the team, it might reset the progression of the TF, resulting in a repeated mission.

If I started with a single person inviting the whole team and then starting the TF (like you did when you re-started the ITF), I never encountered the issue, no matter who dropped.

*I'm not completely sure if this is the reason or not. I can only provide info about a trend that I noticed. Whether or not my trend is purely imaginary, or if the server somehow mixes up who is the true TF leader.. your guess is as good as mine.

When this has happened to me, we have always been able to continue the TF by trying the following:
1) Have other people try to call the contact, particularly if you can remember who had the star before.
2) Have the leader log out and back in.
3) As a last resort, have EVERYONE log out and back in.

Glad I found this thread. This has happened to me twice now. Some data in case it helps:

First time: Sister Psyche TF a couple weeks ago when it was the WST. Star was passed before starting. In the second mission, I think the original star bailed, but it may have been someone else. In either case, the mission bugged.

Second time: ITF tonight. The star was passed from a 45 to a 50 before the TF began, and during the second mission a random teammate (not either star) bailed, bugging the mission.

Next time it happens I'll have to keep your tips in mind, Ironblade. Thanks.

Interestingly, another ITF I ran earlier tonight had a different but possibly related bug. A 38 had the star and passed it to a 50. During the first mission the starred 50 disconnected but did not leave the TF. The star got automatically handed back to the 38. The mission did not bug, but instead of us 50s either staying at 50 or exemping down to 38, we were exemped to 49. As it wasn't a showstopper glitch, we carried on with the TF to completion.

We pass the star all around prior to starting TF's all the time and it has never bugged the TF. When we get bugged it is always because someone dropped just prior or during a mission and it doesn't have to be the star. It seems pretty random in that the TF does not always become bugged because someone dropped.

It has happened to me several times in PuG TF's but only once to our SG. All times it has happened to me we waited 15 minutes or so for a GM to fix it. Next time it happens to a SG run I'll suggest Ironblade's solution.

Luckily it doesn't happen to us often because people drop so rarely (and when they do it is a controlled "I need to reboot" kind of drop). In fact the one time it did happen to us it was a person who joined just to fill so we could start. After we started they went to Ouroboros and exited the game then came back a little later and quit the TF to go do something else.

Doesn't happen to me all the time but it has happened before.

We call it groundhog day. Means that as a minimum the 'leader' has to log out and back in to force the star to be passed. In extreme cases everyone logs out and back in.

Seems to us the symptom is that the mish is repeated along with the identical map, and the leader didn't have to call it in to receive the repeated mission. Also calling the contact doesn't seem to do anything for the leader.

Seems to be triggered by someone quitting the task force. Not sure what other conditions must be met for the problem to happen (ie. different zone or before/after the mission has been set etc. or rogues/vigilantes being on a team).

I got a new version of this issue the other day.
1. Positron TF and the person assembling the team is level 12 so passes the star before we start.
2. Someone has an emergency and quits during the first mission.
3. We do the second mission and it repeats.

I explain the steps that should fix it. Leader and one other person immediately start logging. I wait to see if the leader logging will help.

Here's the good part: when those two people logged in, they were A NEW TEAM. They did not show the rest of us on their team and they did not appear on our team. They DID have the next TF mission ready to go. So, the rest of us re-logged. As we did so, each person dropped off the team stuck on the previous mission and became part of the new team with the correct mission.

Weird, eh? I wonder if this is what was happening all along, but I never saw it because we would usually have the entire team re-log at once.