nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Updated Chase connection - bill still says 'needs attention'

mrpaley1

A while ago, I updated the Chase bill connection so I have the new 'check pay' drop down. It continues to retrieve the 'due' amounts which is all I need it for. However, it also said 'needs attention" and is pinned to the top. Today, the Chase account connection converted with the Chase website authorization. I figured maybe at this point the bill area would stop reporting 'needs attention' but it still appears this way. When will this go away?

Find more posts tagged with

Comments

Tungue

I am having the same issue. Have you heard anything from support yet?

jakugler

I'm also having this issue. No one has provided a resolution?

Tungue

I have not received a reply or found any other posts addressing this issue. The problem still seems to be going on after the latest software update.

erlem.218

Same here. Can someone please respond to this?

pkelley

Received update (R43.26) this morning. Still have Chase showing "Needs Attention" in Bills & Income.

dawncpa311

I have the same issue. I would like to opt out of seeing that since I don't want to use Check Pay.

dwtcpa

I am having the same issue.

James118

I am having the same issue.

xlnja

I have the same issue.

Jim Driscoll

I have the same issue! I have removed the account and added it back several times and still see the message "Needs Atention" but only in the "Due Date' view. The message is not there if I view my bills in the "Biller Name" view. No error codes are present with the "Needs Attention" message.

Bob Stevens

I'm in the same boat as well. I had reached out to Quicken support and was instructed to remove the Chase accounts so they could repair something on the back end, wait 3 days, and then readd and I should see the problem resolved. I waited 10 days and readded as directed, but the problem instantly reappeared. I've reached out to Quicken support again -- > 1 week has passed and they haven't even responded. Clearly this is a widespread issue...

Tungue

It looks like the latest update (Version R44.20, Build 27.1.44.20) has fixed the issue.