You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After having added secrets from Gocardless to Actual and trying to create a new linked account or link an existing account (both equally end with the same problem) a new tab opens for Gocardless. I go through the regular process and end up authenticating and authorizing the connection with my bank. After successfully authorizing the connection, the tab hangs for several minutes (normally ~15 minutes) before closing. After 10 minutes (ie. before the bank tab closes) the Actual tab reports that the process has timed out.
I have verified that Gocardless can connect to my bank as it works in the Gocardless developer portal. I reached out to Gocardless support that verified my connection and told me that authorization with the bank works fine and that they succesfully get data back from my linking request, but before that happens, Actual has timed out. Gocardless suggests increasing the time-out window to allow for a slow integration between Gocardless and the bank. I have tried setting a starting balance on the account in the hopes that that would reduce the number of transactions and thus reduce the required time frame for linking, but it makes no difference.
I have attempted to reach out to the Discord community to no avail.
How can we reproduce the issue?
Link an existing account or create a new linked account. Go through the process and if the loading from the bank back to Gocardless takes more than 10 minutes, Actual times out regardless of (later) success.
I've tried both with local docker hosting as well as Pikapods. I've tried with multiple browsers; Edge, Chrome, Firefox and Edge Android, same result.
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Microsoft Edge
Operating System
Windows 11
The text was updated successfully, but these errors were encountered:
I'm experiencing the same issue with "bank sync". I have three linked accounts and each time I try to sync them, at most one of the accounts are getting synced.
Same thing happens for me since today. Yesterday the initial linking was working fine, today - testing in a new Actual instance, it stays forever on the 'Waiting for GoCardless' screen with tons of POST requests to /account-data in the server logs.
Verified issue does not already exist?
What happened?
After having added secrets from Gocardless to Actual and trying to create a new linked account or link an existing account (both equally end with the same problem) a new tab opens for Gocardless. I go through the regular process and end up authenticating and authorizing the connection with my bank. After successfully authorizing the connection, the tab hangs for several minutes (normally ~15 minutes) before closing. After 10 minutes (ie. before the bank tab closes) the Actual tab reports that the process has timed out.
I have verified that Gocardless can connect to my bank as it works in the Gocardless developer portal. I reached out to Gocardless support that verified my connection and told me that authorization with the bank works fine and that they succesfully get data back from my linking request, but before that happens, Actual has timed out. Gocardless suggests increasing the time-out window to allow for a slow integration between Gocardless and the bank. I have tried setting a starting balance on the account in the hopes that that would reduce the number of transactions and thus reduce the required time frame for linking, but it makes no difference.
I have attempted to reach out to the Discord community to no avail.
How can we reproduce the issue?
Link an existing account or create a new linked account. Go through the process and if the loading from the bank back to Gocardless takes more than 10 minutes, Actual times out regardless of (later) success.
I've tried both with local docker hosting as well as Pikapods. I've tried with multiple browsers; Edge, Chrome, Firefox and Edge Android, same result.
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Microsoft Edge
Operating System
Windows 11
The text was updated successfully, but these errors were encountered: