Bank feeds: sync no longer fails on long transaction ids
Enable Banking ids are about 150 characters, so looking up 500 of them in one request made a URL the database gateway turned away. The error was ignored, every row looked new, and inserting them failed on the saved ones (23505), so the connection showed "Needs you to sign in again" and linking again failed too. - saved rows are read by account and date range, in pages, and errors stop the sync - a new row whose id is saved after all is skipped; the same id twice in one fetch is one row - database errors keep their message in the log and on Accounts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
0d399b77c3
commit
fbdeea630a
3 files changed
+43
-29
No files matched your search
@@ -40,7 +40,7 @@ export async function GET(request: Request, { params }: { params: Promise<{ id:
|
||||
}
|
||||
return back("connect=done");
|
||||
} catch (e) {
|
||||
console.error(`[broke] ${id} connect:`, e instanceof Error ? e.message : e);
|
||||
console.error(`[broke] ${id} connect:`, e instanceof Error ? e.message : JSON.stringify(e));
|
||||
return back("connect=failed");
|
||||
}
|
||||
}
|
||||
Reference in new issue
Block a user