Sync for YNAB experienced a notice incident on August 22, 2019 affecting Sync Platform, lasting 14d 13h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 22, 2019, 07:19 PM UTC
We have had to temporarily disable syncing of RBS accounts due to large numbers of duplicate transactions being created. Our data provider are looking into this, and we hope to re enable it as soon as possible.
- identified Aug 23, 2019, 02:41 PM UTC
We are continuing to work with our data provider on a solution to this. Once we know more, we will post an update.
- identified Aug 27, 2019, 01:40 PM UTC
We are still working with our data provider on this. Unfortunately, it looks like a problem with the RBS Open Banking API, which makes these issues very hard and slow to solve.
- identified Aug 28, 2019, 07:55 AM UTC
This is impacting all RBS Group banks, including Natwest. TrueLayer are trying to get some clarification from RBS Group on this issue, and when it will be resolved. At this time, only RBS is disabled. Natwest and Ulster are still enabled (but will still have issues, such as duplicate transactions). We may enable RBS again today, with the caveat that duplicate transactions are likely, as most customers are expressing that this is still worth it vs manual entry.
- identified Aug 29, 2019, 01:18 PM UTC
Later today, we will be enabling RBS again. The issue is still present, but customers have expressed that they would much rather have duplicate transactions vs no transactions at all. Customers have been emailed explaining the situation, and what to do if you do not want this enabled.
- monitoring Aug 29, 2019, 02:08 PM UTC
RBS Syncing has now been enabled again.
- identified Sep 03, 2019, 02:58 PM UTC
RBS Group have acknowledged this issue, and are working on a fix.
- monitoring Sep 05, 2019, 10:16 AM UTC
RBS Group have pushed a fix for this, and the issue should now be resolved. Please reach out if you are still experiencing these issues.
- resolved Sep 06, 2019, 09:02 AM UTC
This incident has been resolved.