Nationwide Retirement Login giving error FDP 102

@FutureEye, thanks for reaching out to the Community!

When checking your connection attempts with Nationwide Retirement Solutions from our end, I am able to confirm the FDP-102 error. To clarify, is this error occurring on an existing account in Quicken Simplifi, or have you been receiving it since trying to connect for the first time? If the former, I would recommend following these steps to establish a completely fresh connection with the bank:

1. Make all of the accounts with this bank manual by following the steps here.
2. Once you see the account(s) listed in the Manual Accounts section under Settings > Accounts, go back through the Add Account flow to reconnect to the bank.
3. If the connection is successful, carefully link the account(s) found to your existing Quicken Simplifi account(s) by following the steps here. 

Let us know!

@FutureEye, thank you for confirming!

I have submitted this issue to our service provider and will post back here with updates.

EWC-12077695

@FutureEye, thank you for confirming you can participate in the session!

It looks like we will also need this piece of data from you (feel free to DM it to me for privacy):

• A screenshot of the Accounts Summary page from the bank's website that has a wide enough scope to show the full page URL. This is the landing page after signing in, and typically lists all accounts and balances. You will want to take this from a web browser and not a mobile browser, as well as redact any private info such as account numbers.

And we will also need logs to be submitted via the 'Send Feedback' option:

1. Log in to the Quicken Simplifi Web App.
2. Select Profile from the left-hand navigation bar.
3. With the Profile menu open, hold down the Option key for Mac or the Alt key for Windows, and then click Send Feedback. 
4. Leave all boxes checked, add a brief description of the issue, and then click Send.

@danielp_, thank you for joining the discussion!

It sounds like you are likely experiencing the same thing. Once we get the HAR file session requested for @FutureEye, I would definitely recommend following along here for updates, as the fix for this should be global.

@FutureEye, were you able to gather the above data and send logs, by chance?

Once we have that data, we can request the session!

@FutureEye, thank you!

I have filed a ticket to request the session. Please keep an eye on your email, as someone from our engineering team will reach out to confirm a set date and time (this may take a few days to weeks before you hear from someone). Otherwise, I will keep you updated here with anything I see come through on my end.

CTP-15565