Pending transaction imports, android devices, and digital dinosaurs
To all ye present, greetings! My digital dinosaur and I both have an android device with which we do most of our YNAB tracking on. For some reason, unknowable to me, I am the only one that will actually use the computer's digital superhighway onramp for YNAB, and I only look towards sage council (at the blog/forums) when something doesn't work.
As a consequence of this, the Pending Transaction Importing feature that just rolled out (for us), came as a shock to my dinosaur and me. This new feature showed 34 transactions
The inability to interact with these duplicate entries for transactions we had recorded manually, including some transactions that had cleared in the bank, and even duplicate pending transactions caused great angst for my dinosaur and the roars of frustrations towards their robotic device were mighty. I was given a quest to "figure it out and make it work again." With great urgency, I went forth to restore tranquility to the realm. Deep behind the enemy fire-walls, I braved viruses innumerable while the routers lit up like Christmas trees as they were attacked by enemies born horseback or that burrowed beneath the surface as beings meant to feed fish.
Arriving at the foretold battlefield (YNAB.com) I methodically selected every transaction that had shunned our overtures on android (all the pending transactions). I then rejected each and everyone, banishing them from our sight. It seemed that I had restored tranquility to the realm.
I then sought out the sage council for ways to prevent future reoccurrence. There I discovered that to reject an import is to banish it forever, never shall it import again. Or at least that is how it was in the before times.
Will these rejected pending transaction imports return when they are real, posted, and cleared transactions? Or will I have to manually clear each entry as it posts? How can I get android to just not display them until I can interact with them?
My dinosaur is unlikely to learn new tricks.
Cohen So sorry these pending transactions have caused some turmoil in your domain! I want to give you some answers, as well as ask a few more questions:
- The cleared versions of those rejected pending transactions should still import and match up with any manually entered versions.
- Unfortunately, pending transactions can't be turned off - but we can talk about some ways to manage them! Before we dive into that, can you clarify for me...
- Are you manually entering all of your transactions prior to the pending versions importing?
Cohen Those imported pending transactions should match up with the manual versions that your local dinosaur is dutifully entering and not clutter up your view on Android. 🤔I wonder if your pending transactions are erroneously importing more than once. Would you be up for enabing Support Access so we could take a look at those specific transactions that didn't match as expected? Let me know when you've done that and have some examples - we'll take it to email from there!
The good news is that our Android devs are working on making sure you are able to interact with those transactions, just as you can in the web and on IOS.