github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #8087] [Bug]: PluggyAI service is using the deprecated fetchTransactions method #117669

New Issue
Open
opened 2026-06-11 13:07:11 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-11 13:07:11 -05:00
Owner
Copy Link

Originally created by @hfoletto on GitHub (Jun 4, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/8087

What happened?

When setting up a Pluggy.ai connection, the account links successfully, but the initial sync immediately fails.

Image

Inspecting the server logs shows the following error:

[Pluggy SDK] HTTP request failed: Response code 410 (Gone) {
  message: 'This endpoint is deprecated. Use GET /v2/transactions with cursor pagination instead.',
  code: 410,
  codeDescription: 'ENDPOINT_DEPRECATED',
  errorId: '[...]'
}
Error fetching transactions: This endpoint is deprecated. Use GET /v2/transactions with cursor pagination instead.

The error appears to originate from the transactions fetch call in the Pluggy integration:

https://github.com/actualbudget/actual/blob/v26.6.0/packages/sync-server/src/app-pluggyai/pluggyai-service.js#L75

The Pluggy Node SDK repository recently added a deprecation notice for the endpoint currently being used:

https://github.com/pluggyai/pluggy-node/pull/165

According to the Pluggy API documentation (https://docs.pluggy.ai/reference/transactions-list-1):

Deprecated: this endpoint is deprecated and will be available only until 2026-12-31, after which it will be removed. Please migrate to GET /v2/transactions, which uses cursor-based pagination.

Although the documented removal date has not yet been reached, the endpoint is already returning HTTP 410 (Gone).

To verify this was not specific to Actual Budget, I attempted to call the endpoint directly through Pluggy's API explorer and received the same response:

Image

This suggests the issue is not with Actual itself, but rather that Pluggy is already rejecting requests to the deprecated endpoint.

Expected behavior

Actual should fetch transactions successfully through Pluggy.ai.

Actual behavior

The account links successfully, but transaction synchronization fails immediately with HTTP 410 because the integration is still using a deprecated transactions endpoint.

Suggested fix

Migrate the Pluggy integration to use the newer GET /v2/transactions endpoint with cursor-based pagination, as recommended by Pluggy.

How can we reproduce the issue?

  1. Setup the Pluggy.ai integration following this: https://actualbudget.org/docs/advanced/bank-sync/pluggyai/
  2. Link an account
  3. See the error

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Windows 11

Originally created by @hfoletto on GitHub (Jun 4, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/8087 ### What happened? When setting up a Pluggy.ai connection, the account links successfully, but the initial sync immediately fails. <img width="525" height="141" alt="Image" src="https://github.com/user-attachments/assets/a3f5ee54-0133-47c4-a6f4-a85fde21890b" /> Inspecting the server logs shows the following error: ``` [Pluggy SDK] HTTP request failed: Response code 410 (Gone) { message: 'This endpoint is deprecated. Use GET /v2/transactions with cursor pagination instead.', code: 410, codeDescription: 'ENDPOINT_DEPRECATED', errorId: '[...]' } Error fetching transactions: This endpoint is deprecated. Use GET /v2/transactions with cursor pagination instead. ``` The error appears to originate from the transactions fetch call in the Pluggy integration: https://github.com/actualbudget/actual/blob/v26.6.0/packages/sync-server/src/app-pluggyai/pluggyai-service.js#L75 The Pluggy Node SDK repository recently added a deprecation notice for the endpoint currently being used: https://github.com/pluggyai/pluggy-node/pull/165 According to the Pluggy API documentation (https://docs.pluggy.ai/reference/transactions-list-1): > Deprecated: this endpoint is deprecated and will be available only until 2026-12-31, after which it will be removed. Please migrate to GET /v2/transactions, which uses cursor-based pagination. Although the documented removal date has not yet been reached, the endpoint is already returning HTTP 410 (Gone). To verify this was not specific to Actual Budget, I attempted to call the endpoint directly through Pluggy's API explorer and received the same response: <img width="558" height="393" alt="Image" src="https://github.com/user-attachments/assets/1c819747-ff94-4d93-b1c5-46c7d826e4ca" /> This suggests the issue is not with Actual itself, but rather that Pluggy is already rejecting requests to the deprecated endpoint. ### Expected behavior Actual should fetch transactions successfully through Pluggy.ai. ### Actual behavior The account links successfully, but transaction synchronization fails immediately with HTTP 410 because the integration is still using a deprecated transactions endpoint. ### Suggested fix Migrate the Pluggy integration to use the newer GET /v2/transactions endpoint with cursor-based pagination, as recommended by Pluggy. ### How can we reproduce the issue? 1. Setup the Pluggy.ai integration following this: https://actualbudget.org/docs/advanced/bank-sync/pluggyai/ 2. Link an account 3. See the error ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Windows 11
GiteaMirror added the help wantedbugbank sync labels 2026-06-11 13:07:13 -05:00
GiteaMirror commented 2026-06-11 13:07:14 -05:00
Author
Owner
Copy Link

@coderabbitai[bot] commented on GitHub (Jun 4, 2026):

🔗 Related PRs

actualbudget/actual#7930 - [AI] Fix off by one error in enable banking [merged]
actualbudget/actual#8006 - [AI] Fix bug when linking accounts [merged]

📝 Issue Planner

Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

  • Create Plan
🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

<!-- gh-comment-id:4625396939 --> @coderabbitai[bot] commented on GitHub (Jun 4, 2026): <!-- This is an auto-generated issue plan by CodeRabbit --> <details> <summary>🔗 Related PRs</summary> actualbudget/actual#7930 - [AI] Fix off by one error in enable banking [merged] actualbudget/actual#8006 - [AI] Fix bug when linking accounts [merged] </details> --- <details> <summary>📝 Issue Planner</summary> <sub>Check the box below or use the `@coderabbitai plan` command to generate an implementation plan and prompts that you can use with your favorite coding assistant.</sub> - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
GiteaMirror commented 2026-06-11 13:07:15 -05:00
Author
Owner
Copy Link

@KevinIsMyName commented on GitHub (Jun 5, 2026):

Hey, I can take a stab at this! Looks like the /v1/transactions removed pagination parameters and the new /v2/transactions wants callers to use the next attribute instead of specifying the next page.

<!-- gh-comment-id:4628782682 --> @KevinIsMyName commented on GitHub (Jun 5, 2026): Hey, I can take a stab at this! Looks like the [/v1/transactions](https://docs.pluggy.ai/reference/transactions-list-1) removed pagination parameters and the new [/v2/transactions](https://docs.pluggy.ai/reference/transactions-list-by-cursor) wants callers to use the `next` attribute instead of specifying the next page.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bank sync bug help wanted
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117669
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?