-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transactions Not Syncing in Polled Mode Without Manual Refresh #69
Comments
I have not personally seen this issue. Do you only see it with a single institution or all your institutions? My first guess is it's an issue on Plaid's end, failing to trigger updates on the I'm not categorically opposed to building this feature in, although the connector doesn't currently have any means of accepting user input, and the pricing for the coming paid cutover looks like it would make this feature expensive. |
I have been experiencing something similar, specifically with Discover (that is the only institution where I make transactions frequently enough to notice a problem). Transactions are only found inconsistently. I hadn't tracked down the exact cause yet. I will try I did find this in the
|
Thank you for sharing your experiences and for referencing the relevant section of the Plaid documentation. Indeed, the portion of the documentation you mentioned guided me to experiment with the The I'm considering developing a smart batch process, potentially leveraging a local SQLite database, to identify and sync missing transactions in Firefly while avoiding duplicates. If you have any suggestions or if there's a potential for collaboration on developing a more refined solution, I'm open to ideas. |
Yeah, I suppose it depends on Plaid's architecture for updating transactions for your particular institution. I assume they have a mix of pull and push models depending on the API for each institution. If a manual refresh works and the automatic, periodic refresh doesn't, I would infer that they use different methods (i.e. your bank pushes to Plaid automatically, manual refresh does a full pull on another endpoint).
Sure, that seems straightforward enough to do what you want. I'm also not opposed to adding something like that to the connector, but as previously mentioned I don't think it's going to have much long term value.
I would need some more details on what you're trying to accomplish and how you're planning on doing it before I can really offer anything, but happy to talk about ideas. |
I looked up the institutions I was having problems with on https://dashboard.plaid.com/activity/status and they either have limited availability based on the time of day or have a overall poor success rates. So I would say this is definitely not a problem with the connector. But as a work around, I wouldn't mind an option to automatically refresh every x amount of time. Although that might be more trouble than its worth. Its another thing to track. And you would have to account for institutions limited availability periods, there is no point in refreshing when the institution is limited. Although the billing for |
I can confirm that
I didn't realize the endpoint reports time in UTC so I thought the institutions were up to date when in fact they weren't. |
I have noticed the same problem in my account (I currently only have one). fireflyPlaidConnector2:
accounts:
- fireflyAccountId: X
plaidItemAccessToken: access-environment-xyz
plaidAccountId: abc
forceRefresh: true|false
refreshInterval: 60 # minutes |
When operating in polled mode, I've encountered a consistent issue where transactions are not being automatically added to Firefly. This occurs despite waiting for periods extending beyond 24 hours. The transactions only appear after manually triggering a refresh using a cURL request to
/transactions/refresh
.As a workaround, I am considering implementing an automated task to trigger
/transactions/refresh
every hour. However, this is not an ideal long-term solution, and I am seeking insights into the root cause and potential fixes.The text was updated successfully, but these errors were encountered: