🛑 Fixed: Delete All could unfriend the wrong person
- Rows were matched by the start of a name, and the app took the first match on the page. A deactivated entry named "Clint" also matched an active friend called Clint Riggin, so the wrong person was unfriended. On the run where we caught it, 21 of 22 removals were correct and one was not.
- Names are now matched exactly, and when two rows could both be the person the app refuses that row instead of guessing. Unfriending cannot be undone, so skipping a row and catching it on the next pass is the safer trade.
👥 Fixed: Deactivated Friends could act on the wrong account
- The bulk unfriend on Deactivated Friends ran without checking which client it belonged to, so a list gathered under one account could be acted on while you were operating as another.
- It now checks first and refuses rather than acting on data it cannot attribute. Broadcast lists no longer appear across accounts either, and the list writer and reader now agree on which account a list belongs to.
🔇 Fixed: campaigns that stopped without telling you
- An error partway through a send could end a campaign with nothing written to the log at all, so a run that stopped early looked no different from one that finished.
- Pressing Stop could reset the screen while the background sender kept going. Stop now says plainly when it did not go through, instead of showing a stopped campaign that is still sending.
- The Audience Builder ran on your daily schedule with no record of what it did, which made a quiet failure impossible to diagnose. It now logs each stage.
📋 Fixed: a failed scan could make engaged people look inactive
- The Inactive list is built from the reactions and comments the app captured. If a scan failed it recorded nothing, so people who really did engage scored zero and were suggested for removal.
- A scan that could not finish now says so and warns you not to trust the list until it is re-run.
🗓️ Fixed: schedules that would not save, silently
- Replacing an existing schedule on Mass Messenger or the Audience Builder could fail with no message, so you would set it, see nothing, and find later it had never saved.
- Both now tell you what went wrong, including when the schedule settings cannot produce a valid next run time.
- Deleting a campaign or list that had a schedule now warns you if the schedule could not be cleared, rather than leaving it waking for something that no longer exists.
🔐 Changed: the app protects a run in progress
- Logging in, switching the session or clearing the browser while an automation is running would swap the account underneath it, sending the rest of the run from the wrong profile. Those actions are now refused while a run is in flight, and they tell you why.
- Error messages across the app were showing raw internal text, or nothing at all. They now show the actual reason.