Nordigen reader skips all accounts after first account which is not found in NORDIGEN_ACCOUNTMAP

[hpernu]

If a session to a particular bank has already been established and/or you've selected accounts that you actually don't have in account map, reader may skip importing data to some accounts.

The reader goes through all of the accounts it has established a connection with Nordigen API. If the account is found on account map, the transacation are read. If not, it skips the account and all the rest of the accounts are skipped as well.
If the account map happens to contain accounts which are on start of the internal order the reader is using (i.e. in the order it got from Nordigen API), then no accounts are skipped.

This is not considered an error.

The behavior is not consistent and is dependant on the order of accounts from Nordigen API. This order is outside of user control.
The user also cannot effectively modify the account map if he/she decided to remove one account from imports. This might or might not work depending on the order they have been fetched via Nordigen API.

Instead of skipping all the rest of accounts after a single miss, reader should instead go to next account. This will allow the modification of the account map(or at least removal of accounts) without reinitializing Nordigen connection.

This is likely a single line change.