Quicken Nordstrom "Multifactor authentication failed"..

snafner

..with a huge stack dump:

This connection failed, and will not update:

     Nordstrom Card Account(JALAYNEF) - Error FDP-101 (CP_SCRIPT_ERROR -  Could not Execute '@.scraper.scrapediv' at Position(file=acquire.isl, line=144, column=25, endLine=144, endColumn=97).

Could not Execute '@.this.getfieldvalue' at Position(file=scraper.isl, line=40, column=20, endLine=40, endColumn=93).

Could not Execute '@.this.getfieldvaluebasedonpath' at Position(file=scraper.isl, line=304, column=18, endLine=304, endColumn=89).

Could not Execute '@.this.getfieldvaluefrompage' at Position(file=scraper.isl, line=420, column=15, endLine=420, endColumn=66).

Could not Execute '@.hb.element'. Error='PlaywrightException: Error { message='Error: strict mode violation: locator("//div[contains(@class ,'transactions-list-container')]").locator("//div[@class ='bb-card__body']").first().locator("//tdb-transactions-list-ui//div[contains(@class ,'transaction-group__date')]") resolved to 4 elements:

    1) <div tabindex="0" role="heading" aria-level="2" class…> November 21, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("November 21,"))

    2) <div tabindex="0" role="heading" aria-level="2" class…> November 6, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("November 6,"))

    3) <div tabindex="0" role="heading" aria-level="2" class…> October 24, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("October 24,"))

    4) <div tabindex="0" role="heading" aria-level="2" class…> October 7, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("October 7,"))

  name='Errorstack='Error: Error: strict mode violation: locator("//div[contains(@class ,'transactions-list-container')]").locator("//div[@class ='bb-card__body']").first().locator("//tdb-transactions-list-ui//div[contains(@class ,'transaction-group__date')]") resolved to 4 elements:

    1) <div tabindex="0" role="heading" aria-level="2" class…> November 21, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("November 21,"))

    2) <div tabindex="0" role="heading" aria-level="2" class…> November 6, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("November 6,"))

    3) <div tabindex="0" role="heading" aria-level="2" class…> October 24, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("October 24,"))

    4) <div tabindex="0" role="heading" aria-level="2" class…> October 7, 2025 </div> aka getByRole(AriaRole.HEADING, new Page.GetByRoleOptions().setName("October 7,"))

    at CRExecutionContext.evaluateWithArguments (/app/tmp/playwright-java-12715364692831257826/package/lib/server/chromium/crExecutionContext.js:92:33)

    at async LongStandingScope._race (/app/tmp/playwright-java-12715364692831257826/package/lib/utils/manualPromise.js:96:14)

    at async evaluateExpression (/app/tmp/playwright-java-12715364692831257826/package/lib/server/javascript.js:241:12)

    at async /app/tmp/playwright-java-12715364692831257826/package/lib/server/frames.js:635:22

    at async Frame.retryWithProgressAndTimeouts (/app/tmp/playwright-java-12715364692831257826/package/lib/server/frames.js:923:24)

    at async /app/tmp/playwright-java-12715364692831257826/package/lib/server/frames.js:621:14

    at async ProgressController.run (/app/tmp/playwright-java-12715364692831257826/package/lib/server/progress.js:82:22)

    at async FrameDispatcher.waitForSelector (/app/tmp/playwright-java-12715364692831257826/package/lib/server/dispatchers/frameDispatcher.js:106:85)

    at async LongStandingScope._race (/app/tmp/playwright-java-12715364692831257826/package/lib/utils/manualPromise.js:96:14)

    at async FrameDispatcher._handleCommand (/app/tmp/playwright-java-12715364692831257826/package/lib/server/dispatchers/dispatcher.js:96:14)}

Call log:

- waiting for locator("//div[contains(@class ,'transactions-list-container')]").locator("//div[@class ='bb-card__body']").first().locator("//tdb-transactions-list-ui//div[contains(@class ,'transaction-group__date')]")

' at Position(file=scraper.isl, line=449, column=18, endLine=449, endColumn=43).)

snafner

Today's error is somewhat more succinct:

This connection failed, and will not update:

     Nordstrom Card Account(JALAYNEF) - Error FDP-101 (CP_SCRIPT_ERROR -  dateFormat is not available for the given input date : November 6 2025)

To retry the failed connection, you'll need to start a new update.

Quicken Anja

Hello @snafner,

Thanks for the detailed information.

The FDP-101 error you're seeing is generated when Quicken is unable to successfully connect to the financial institution to retrieve transaction data. While the error text can sometimes look very technical (as in your stack output), the underlying issue is that the connection attempt isn’t completing as expected.

The stack trace you posted suggests the Nordstrom site structure or date formatting changed, causing Quicken's connection script to fail during the scraping process. That aligns with the FDP-101 definition: the connection is initiated, but Quicken is unable to complete it and retrieve data.

Please review this support article regarding this error.

To resolve this issue:

• Wait 24 hours and try again.
• If the error persists after waiting 24 hours, please contact Quicken Support so our teams can collect logs and escalate if needed.

Thank you!

ncsuaaronf

I am experiencing this same issue. I have disconnected and attempted to started over.

Quicken Anja

Hello @ncsuaaronf,

Thanks for sharing your experience.

As mentioned in my previous response above, the FDP-101 error occurs when Quicken can’t fully complete the connection to the financial institution to download transactions. Even if you start over or disconnect/reconnect, the underlying issue is usually on the site’s end—for example, changes to the site structure or date formatting that Quicken’s connection script relies on.

The best next step is to wait about 24 hours and try again. If the problem continues beyond that, please contact Quicken Support so they can collect logs and escalate the issue if needed.

Thank you!