Never Miss a PMS Sync Failure Again

Release v0.1.254 | Notification Workflow

---

Property Management System integrations are the backbone of automated tenancy workflows. When they break silently, the knock-on effects — stale records, missed move-outs, incorrect deposit data — can compound quickly before anyone notices.

With v0.1.254, that silent failure mode is gone.

What We Shipped

We've added an automated notification workflow that fires the moment a PMS sync marks itself as failed. As soon as the pms-connection-sync service records a status=error, the platform:

1. Identifies the affected connection and retrieves the error details.
2. Finds every Admin and Owner in the impacted organisation.
3. Sends an urgent in-app notification and an email to each of them — immediately.

The notification tells them exactly which integration failed, what the error was, and includes a direct link to the integrations settings page so they can act without hunting through menus.

Why Event-Driven?

This workflow is triggered by the pms/connection.sync.failed event rather than a scheduled poll. That means there's no lag — admins are informed within seconds of a failure, not the next time a cron job happens to check.

Who Sees It

Only Admins and Owners receive these notifications. They're the people with the access and responsibility to fix integration issues. Standard members aren't alerted, keeping noise low for users who can't action the problem anyway.

Keeping Deposit Workflows Intact

At DepositLink, fair and fast deposit resolution depends on accurate, up-to-date tenancy data. A PMS sync failure is an early warning signal — and now, it's one that gets heard immediately by the people who can fix it.

---

Available from v0.1.254. See the feature documentation for full details.