Never Miss a Sync — Introducing AgentOS Failure Escalation

Release v1.0.25 | Workflow Update

Keeping your property transactions up to date is central to meeting your Making Tax Digital obligations. That means your AgentOS connection needs to be working — reliably, every day. Starting with v1.0.25, the platform actively watches that connection for you and speaks up the moment something goes wrong.

The Problem

AgentOS integration is how your rental transactions flow into the platform and ultimately into your quarterly HMRC summaries. When that sync breaks — due to expired credentials, a network interruption, or an API issue — transactions stop arriving silently. You might not notice until you review a quarterly summary and find it looking unexpectedly thin.

By then, you may have already missed several weeks of rent payments, expenses, and fees. Correcting that before a submission deadline adds unnecessary stress.

What's New in v1.0.25

We've introduced a daily escalation workflow that sweeps all AgentOS connections each morning and checks whether any are stuck in an error state. If yours has not synced successfully in the past 24 hours, you'll hear about it immediately.

24 hours — first alert

An in-app notification and an email land with your org owner:

"Your AgentOS connection has not synced in {N} hours. New transactions may be missing from your quarterly summaries."

This gives you plenty of runway to investigate and fix the issue well before it affects anything meaningful.

72 hours — escalation

If the connection is still broken after three days, a second, higher-urgency alert is sent. At this point, the message is direct: your current quarterly summaries may already be incomplete and you should act before your next HMRC submission.

Designed Around Your Submission Deadlines

MTD ITSA quarterly submissions don't wait. If transactions are missing when you file, you risk inaccurate figures with HMRC — and potentially penalties down the line. This workflow is designed so that a sync failure never quietly compounds in the background. You get an early warning, then a firm nudge, with enough time to resolve it cleanly.

What You Should Do If You Receive an Alert

1. Go to Settings → Integrations → AgentOS and check the connection status.
2. Re-enter your AgentOS credentials if they've expired.
3. Trigger a manual sync to pull in any missed transactions.
4. Review your quarterly summary to confirm all transactions are present.

Under the Hood

The workflow runs on a cron schedule at 08:00 UTC every day. It queries all agentosConnections where status = 'error' and lastSyncAt is older than 24 hours, then fires notifications through the platform's notification system to the relevant org owner.

---

This release ships no UI changes — just a smarter, more watchful backend that keeps your tax data accurate without requiring you to manually check integration health.

As always, if you have questions about your AgentOS connection or your quarterly summaries, reach out via the in-app support channel.