Yesterday I made a scheduled fireteam post for today at 11am EDT, for a triumph in Crota's End.
Overnight, 5 people joined the scheduled fireteam. I got notifications in the bungie companion app, and when I tapped on a notification I could see the scheduled fireteam with each of the names filling each slot.
This morning I pulled up the Bungie web site, logged in, clicked Community -> Find Fireteam -> My Fireteams, and my scheduled fireteam was not there.
Confused, I clicked on the notifications bell and saw that it still had the history of all the players who joined. I clicked through there and I found my scheduled fireteam.
Then I clicked invite all. The buttons showed all invites sent. Nobody joined. At this point I'm not confident that the invites were actually sent, because of the backwards way I had to get into the fireteam post itself.
So in-game, I manually searched for each of the players, so that I could send them an invite in-game. Every player I searched and found said "Offline" and the "invite" button was greyed out.
Ok, I could see how maybe some people might sign up but ghost the actual activity, but all 5 of them? Didn't seem right. I clicked through one of the profiles on Bungie.net and saw that it was an Xbox player. I'm on Xbox. I searched in Xbox and found the player, and Xbox says this person is online playing Destiny in Crota's End. So they're playing the game, but the in-game search says they're offline and I couldn't invite them. That's broken.
It's now 15 minutes past the scheduled time of the activity and I've sent multiple invites via the website and nobody has joined. Am I just unlucky and 5 out of 5 are are ghosting me, or are the invites not really going out to those players? How can I tell the difference between bad luck and a bug?
-
In any case, this is a big turn-off from using the Scheduled Fireteams feature. I'm really disappointed. I was optimistic when I saw that 5 people had joined. And now that zero of them have responded to my fireteam invite, I'm annoyed. It makes me want to not bother trying to use this feature again.