Bug Fixes

Issue: Error message occurred when trying to remove a customer's pending bank account from the CRM.

Resolution: Fixed an issue with the connection to Stripe's API, so users can now successfully delete unverified bank accounts.

Issue: Users experienced an issue where the Text Messages list would get stuck with an infinite loading wheel when searching using an apostrophe (’).

Resolution: Fixed the problem so that searches using an apostrophe now work normally and no longer cause infinite loading.

Issue: Users were unable to add more than one "Stop" action within a Sequence Automation, which limited the flexibility of how automations could be set up.

Resolution: This has been resolved so users can now add multiple "Stop" actions in a single Sequence Automation, allowing for more control over when and how sequences end.

Issue: The "Events Assigned to This Property" section on Properties was displaying events out of chronological order, making it hard to follow the correct timeline.

Resolution: Fixed the sorting logic so that events now appear in proper chronological order, making it easier to track the sequence of activity for each property.

Issue: When users clicked a customer’s name on the Text Messages page, it incorrectly opened a deleted version of the customer profile instead of the current, active one.

Resolution: This issue has been resolved so that clicking a customer’s name now always takes you to the correct, active profile associated with the message, ensuring deleted profiles are not mistakenly accessed.

Issue: The "Show Account Standing" setting was incorrectly affecting the visibility of "Paid", "Outstanding", and "Past Due" roll-ups on the My Day page, even though it was only meant to affect "Paid".

Resolution: Fixed the issue so that the "Show Account Standing" setting now only applies to the "Paid" roll-up, and no longer impacts "Outstanding" or "Past Due".

Issue: When switching between different actions in Sequence Automations, the actions could sometimes behave irregularly, leading to unexpected or incorrect automations being triggered.

Resolution: Fixed the issue so that switching between actions in Sequence Automations now works properly, ensuring expected Sequence Automation configuration.