Re: Do "Pending Transactions" ever leave the list?

On 12/15/2024 10:26 AM, Andrew wrote:
> On 12/14/2024 10:05 AM, tmp6986 wrote:
>> On 12/13/2024 9:07 AM, Andrew wrote:
>>> So I set the option to view the pending transactions when I d/l them 
>>> to my QFW credit card accounts.  The panel shows "Downloaded 
>>> Transactions", "Bill and Income Reminders", and "Pending 
>>> Transactions" below the register.
>>>
>>> But I have quite a few transactions in this Pending list that I 
>>> already have downloaded and accepted as cleared weeks ago.  They're 
>>> duplicates in the sense they are already in the register and also in 
>>> the pending list.  For example, a AMAZON charge I made on 12/1 that 
>>> was downloaded and cleared in my register on 12/2 still is in the 
>>> PENDING TRANSACTION list.
>>>
>>> So up to now, I've simply been manually deleting them via the DELETE 
>>> button....but does anyone know if these will go away on their own 
>>> when either Q or the FI 'understands' they have been accounted for a 
>>> long time ago?
>>>
>>> I would have expected them to go away as soon as they are accepted 
>>> into my register when doing the OSU into the charge account.
>>
>> FWIW, I've seen the same thing happen here, although it doesn't happen 
>> very often. The vast majority of the pending transactions disappear 
>> from the Pending Transactions list automatically when they should. For 
>> the few that do get stuck in the Pending list, I have just manually 
>> deleted them (as you are doing) without any further issues.
>>
>> (I'm running Quicken Classic Premier R60.15)
> 
> TU.  Glad I'm not alone :-)  .  I guess if others like you have seen 
> this, I'll raise a comment in the Quicken Community forum and see what 
> they have to say.
> 

So others have this problem as well.  One of the Q folks asked me for 
all sorts of information about my configuration etc. which I just wasn't 
in the mood to try to provide....not worth the effort. I manually 
deleted this one transaction in the pending panel and hopefully it was a 
one-off fluke, or at least not worth the effort to get resolved if it 
doesn't occur frequently. Got to pick your battles.

Case closed here, I hope.

-- 
-----------------------------------------------------------
Regards -

- Andrew