github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: synching error actual #2803

New Issue
Closed
opened 2026-02-28 20:28:50 -06:00 by GiteaMirror · 18 comments
GiteaMirror commented 2026-02-28 20:28:50 -06:00
Owner
Copy Link

Originally created by @ivar2912 on GitHub (Jan 11, 2026).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I am using Lunchflow to import transactions into Actual. While the terminal finds the transactions and loads them into Actual I get the following error: ''We had problems syncing your changes. Please report this as a bug by opening a GitHub issue.' 'No transactions show up in Actual till the next day around 7 P.M if I load them in manually threw the terminal. I am running Actual on a self hosted docker in Unraid. I have a cron job set up for auto-import which also does not work because of this issue. The customer service of Lunchflow did not find any issues on their side. They said the issue lies with Actual.

How can we reproduce the issue?

How can we reproduce the issue?

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @ivar2912 on GitHub (Jan 11, 2026). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I am using Lunchflow to import transactions into Actual. While the terminal finds the transactions and loads them into Actual I get the following error: ''We had problems syncing your changes. Please report this as a bug by opening a GitHub issue.' 'No transactions show up in Actual till the next day around 7 P.M if I load them in manually threw the terminal. I am running Actual on a self hosted docker in Unraid. I have a cron job set up for auto-import which also does not work because of this issue. The customer service of Lunchflow did not find any issues on their side. They said the issue lies with Actual. ### How can we reproduce the issue? How can we reproduce the issue? ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the bank syncneeds info labels 2026-02-28 20:28:50 -06:00
GiteaMirror commented 2026-02-28 20:28:52 -06:00
Author
Owner
Copy Link

@shellixa commented on GitHub (Jan 11, 2026):

same issue on v26.1.0, Deployment using Docker; Client: Arch Linux + Firefox 146.0.1

Looking into the container logs, there are no errors logged, so the issue must be client-side.

Looking into the browser console, the error "Error: no such column: custom_reports.trim_intervals" is repeatedly logged.

@shellixa commented on GitHub (Jan 11, 2026): same issue on v26.1.0, Deployment using Docker; Client: Arch Linux + Firefox 146.0.1 Looking into the container logs, there are no errors logged, so the issue must be client-side. Looking into the browser console, the error `"Error: no such column: custom_reports.trim_intervals"` is repeatedly logged.
GiteaMirror commented 2026-02-28 20:28:52 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 11, 2026):

Image same problem persists after going back to version v25.12.0.

Image
@ivar2912 commented on GitHub (Jan 11, 2026): <img width="1180" height="852" alt="Image" src="https://github.com/user-attachments/assets/e778d693-29c8-4975-ad21-3a6669cdf2ef" /> same problem persists after going back to version v25.12.0. <img width="637" height="211" alt="Image" src="https://github.com/user-attachments/assets/406582d8-f1a9-48ff-be30-6459fd75063a" />
GiteaMirror commented 2026-02-28 20:28:53 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 11, 2026):

Image Image
@ivar2912 commented on GitHub (Jan 11, 2026): <img width="547" height="78" alt="Image" src="https://github.com/user-attachments/assets/28a257a3-647b-4be8-a6a3-8fecd1070d30" /> <img width="277" height="31" alt="Image" src="https://github.com/user-attachments/assets/c3bc5be0-3fed-421f-bd80-edb6582350b8" />
GiteaMirror commented 2026-02-28 20:28:53 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 11, 2026):

What version of actual are you running on your server and what version of actual are you using via bank sync?

@MatissJanis commented on GitHub (Jan 11, 2026): What version of actual are you running on your server and what version of actual are you using via bank sync?
GiteaMirror commented 2026-02-28 20:28:54 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 11, 2026):

At the moment V25.12.0 but I originally used the latest version V26.1.0. the bank sync is the script of Lunchflow.

@ivar2912 commented on GitHub (Jan 11, 2026): At the moment V25.12.0 but I originally used the latest version V26.1.0. the bank sync is the script of Lunchflow.
GiteaMirror commented 2026-02-28 20:28:54 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 11, 2026):

https://github.com/lunchflow/actual-flow

@ivar2912 commented on GitHub (Jan 11, 2026): https://github.com/lunchflow/actual-flow
GiteaMirror commented 2026-02-28 20:28:55 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 11, 2026):

Yep, that will be the problem. If you used v26.1.0 once - you cannot go back.

I'll keep the issue open for now. We should improve the error messaging around this.

@MatissJanis commented on GitHub (Jan 11, 2026): Yep, that will be the problem. If you used v26.1.0 once - you cannot go back. I'll keep the issue open for now. We should improve the error messaging around this.
GiteaMirror commented 2026-02-28 20:28:55 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 11, 2026):

But the same problem appeared in v26.1.0. So it seems the version does not matter regarding the importing error.

@ivar2912 commented on GitHub (Jan 11, 2026): But the same problem appeared in v26.1.0. So it seems the version does not matter regarding the importing error.
GiteaMirror commented 2026-02-28 20:28:56 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 11, 2026):

What api version number are you using with the lunchflow cli?

Both versions need to be v26.1.0 for things to work for you. Try upgrading everything to the latest version. That should make things work.

I am making an educated guess that lunchflow is using v25.12.0 and your server is v26.1.0.

@MatissJanis commented on GitHub (Jan 11, 2026): What api version number are you using with the lunchflow cli? Both versions need to be v26.1.0 for things to work for you. Try upgrading everything to the latest version. That should make things work. I am making an educated guess that lunchflow is using v25.12.0 and your server is v26.1.0.
GiteaMirror commented 2026-02-28 20:28:56 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 12, 2026):

I found out the API version of Lunchflow is V25.12.0 because this is the latest version they have available. Now it makes sense why the syncing issue appears since I am running Actual on the latest version the client as well as the server. Is there something you guys can do at this point or shall I contact Lunchflow again to check when they are going to update their stuff to v26.1.0?

Image
@ivar2912 commented on GitHub (Jan 12, 2026): I found out the API version of Lunchflow is V25.12.0 because this is the latest version they have available. Now it makes sense why the syncing issue appears since I am running Actual on the latest version the client as well as the server. Is there something you guys can do at this point or shall I contact Lunchflow again to check when they are going to update their stuff to v26.1.0? <img width="893" height="43" alt="Image" src="https://github.com/user-attachments/assets/6758c255-5070-4a55-bc25-2e292d67a8d6" />
GiteaMirror commented 2026-02-28 20:28:57 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 12, 2026):

https://stackoverflow.com/questions/15806152/how-do-i-override-nested-npm-dependency-versions

@MatissJanis commented on GitHub (Jan 12, 2026): https://stackoverflow.com/questions/15806152/how-do-i-override-nested-npm-dependency-versions
GiteaMirror commented 2026-02-28 20:28:57 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 12, 2026):

@coderabbitai please open a new issue: if API and server versions mismatch - throw a friendly error message explaining the problem.

@MatissJanis commented on GitHub (Jan 12, 2026): @coderabbitai please open a new issue: if API and server versions mismatch - throw a friendly error message explaining the problem.
GiteaMirror commented 2026-02-28 20:28:58 -06:00
Author
Owner
Copy Link

@coderabbitai[bot] commented on GitHub (Jan 12, 2026):

🧩 Analysis chain

@MatissJanis I'll create a new issue for this improvement.

🏁 Script executed:

#!/bin/bash
# Create a GitHub issue for API/server version mismatch error messaging

gh issue create \
  --title "Improve error messaging when API and server versions mismatch" \
  --body "## Problem

When the API client version and server version mismatch, the application shows cryptic error messages that don't clearly indicate the root cause. For example, when using an older API version (v25.12.0) with a newer server version (v26.1.0), users see errors like:

\`\`\`
Error: no such column: custom_reports.trim_intervals
\`\`\`

This makes it difficult for users to diagnose that the issue is caused by a version mismatch between the API client and server.

## Expected Behavior

When there's a version mismatch between the API client and server, the application should:
- Detect the version mismatch
- Throw a clear, friendly error message explaining the problem
- Guide users on how to resolve it (e.g., \"API version X.X.X does not match server version Y.Y.Y. Please ensure both are using the same version.\")

## Additional Context

This issue was identified when a user was using the lunchflow tool with API version v25.12.0 while running Actual server v26.1.0.

Backlink: https://github.com/actualbudget/actual/issues/6619
Requested by: @MatissJanis"

Length of output: 50

@MatissJanis I've created a new issue for this: #6633

The issue documents the need to detect API/server version mismatches and provide clear error messages to users, rather than showing cryptic database errors like "no such column: custom_reports.trim_intervals".

🧠 Learnings used 
Learnt from: MatissJanis
Repo: actualbudget/actual PR: 5770
File: packages/desktop-client/src/components/modals/ImportTransactionsModal/ImportTransactionsModal.tsx:818-829
Timestamp: 2025-09-22T20:22:25.375Z
Learning: MatissJanis prefers to keep PR scope isolated to the main objective (like TS upgrades) and avoid including additional patches/improvements outside of that scope, even if they would be beneficial.

Learnt from: MatissJanis
Repo: actualbudget/actual PR: 5770
File: packages/desktop-client/src/components/modals/ImportTransactionsModal/ImportTransactionsModal.tsx:229-230
Timestamp: 2025-09-22T20:22:12.747Z
Learning: MatissJanis prefers to keep TypeScript conversion PRs focused on just the TS upgrade without additional patches/improvements to maintain manageable PR scope.
@coderabbitai[bot] commented on GitHub (Jan 12, 2026): <!-- This is an auto-generated reply by CodeRabbit --> <details> <summary>🧩 Analysis chain</summary> @MatissJanis I'll create a new issue for this improvement. --- 🏁 Script executed: ``` #!/bin/bash # Create a GitHub issue for API/server version mismatch error messaging gh issue create \ --title "Improve error messaging when API and server versions mismatch" \ --body "## Problem When the API client version and server version mismatch, the application shows cryptic error messages that don't clearly indicate the root cause. For example, when using an older API version (v25.12.0) with a newer server version (v26.1.0), users see errors like: \`\`\` Error: no such column: custom_reports.trim_intervals \`\`\` This makes it difficult for users to diagnose that the issue is caused by a version mismatch between the API client and server. ## Expected Behavior When there's a version mismatch between the API client and server, the application should: - Detect the version mismatch - Throw a clear, friendly error message explaining the problem - Guide users on how to resolve it (e.g., \"API version X.X.X does not match server version Y.Y.Y. Please ensure both are using the same version.\") ## Additional Context This issue was identified when a user was using the lunchflow tool with API version v25.12.0 while running Actual server v26.1.0. Backlink: https://github.com/actualbudget/actual/issues/6619 Requested by: @MatissJanis" ``` Length of output: 50 --- </details> @MatissJanis I've created a new issue for this: #6633 The issue documents the need to detect API/server version mismatches and provide clear error messages to users, rather than showing cryptic database errors like "no such column: custom_reports.trim_intervals". --- <details> <summary>🧠 Learnings used</summary> ``` Learnt from: MatissJanis Repo: actualbudget/actual PR: 5770 File: packages/desktop-client/src/components/modals/ImportTransactionsModal/ImportTransactionsModal.tsx:818-829 Timestamp: 2025-09-22T20:22:25.375Z Learning: MatissJanis prefers to keep PR scope isolated to the main objective (like TS upgrades) and avoid including additional patches/improvements outside of that scope, even if they would be beneficial. ``` --- ``` Learnt from: MatissJanis Repo: actualbudget/actual PR: 5770 File: packages/desktop-client/src/components/modals/ImportTransactionsModal/ImportTransactionsModal.tsx:229-230 Timestamp: 2025-09-22T20:22:12.747Z Learning: MatissJanis prefers to keep TypeScript conversion PRs focused on just the TS upgrade without additional patches/improvements to maintain manageable PR scope. ``` </details> <!-- <agentComponentType>chat-answer</agentComponentType> --> <!-- <rawResChunk><answer><details> <summary>🧩 Analysis chain</summary> @MatissJanis I'll create a new issue for this improvement. --- 🏁 Script executed: ``` #!/bin/bash # Create a GitHub issue for API/server version mismatch error messaging gh issue create \ --title "Improve error messaging when API and server versions mismatch" \ --body "## Problem When the API client version and server version mismatch, the application shows cryptic error messages that don't clearly indicate the root cause. For example, when using an older API version (v25.12.0) with a newer server version (v26.1.0), users see errors like: \`\`\` Error: no such column: custom_reports.trim_intervals \`\`\` This makes it difficult for users to diagnose that the issue is caused by a version mismatch between the API client and server. ## Expected Behavior When there's a version mismatch between the API client and server, the application should: - Detect the version mismatch - Throw a clear, friendly error message explaining the problem - Guide users on how to resolve it (e.g., \"API version X.X.X does not match server version Y.Y.Y. Please ensure both are using the same version.\") ## Additional Context This issue was identified when a user was using the lunchflow tool with API version v25.12.0 while running Actual server v26.1.0. Backlink: https://github.com/actualbudget/actual/issues/6619 Requested by: @MatissJanis" ``` Length of output: 50 --- </details> @MatissJanis I've created a new issue for this: #6633 The issue documents the need to detect API/server version mismatches and provide clear error messages to users, rather than showing cryptic database errors like "no such column: custom_reports.trim_intervals". --- <details> <summary>🧠 Learnings used</summary> ``` Learnt from: MatissJanis Repo: actualbudget/actual PR: 5770 File: packages/desktop-client/src/components/modals/ImportTransactionsModal/ImportTransactionsModal.tsx:818-829 Timestamp: 2025-09-22T20:22:25.375Z Learning: MatissJanis prefers to keep PR scope isolated to the main objective (like TS upgrades) and avoid including additional patches/improvements outside of that scope, even if they would be beneficial. ``` --- ``` Learnt from: MatissJanis Repo: actualbudget/actual PR: 5770 File: packages/desktop-client/src/components/modals/ImportTransactionsModal/ImportTransactionsModal.tsx:229-230 Timestamp: 2025-09-22T20:22:12.747Z Learning: MatissJanis prefers to keep TypeScript conversion PRs focused on just the TS upgrade without additional patches/improvements to maintain manageable PR scope. ``` </details> </answer></rawResChunk> -->
GiteaMirror commented 2026-02-28 20:28:59 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 16, 2026):

As you can see below the correct API version is installed. The same error previously mentioned still persists in actual server. I have no clue what the problem can be. Everything is currently on V26.1.0.

/usr/local/lib/node_modules/@lunchflow/actual-flow # cat package.json
{
"name": "@lunchflow/actual-flow",
"version": "0.0.15",
"description": "Import transactions from Lunch Flow to Actual Budget with terminal UI.",
"main": "./dist/index.js",
"bin": {
"actual-flow": "./dist/index.js"
},
"scripts": {
"build": "tsc",
"start": "node dist/index.js",
"dev": "ts-node src/index.ts",
"prepare": "pnpm run build",
"install:dev": "pnpm install",
"clean": "rm -rf dist",
"release:patch": "npm version patch && git push && git push --tags"
},
"keywords": [
"lunch-flow",
"actual-budget",
"importer",
"transactions"
],
"author": "Amr Awad",
"license": "MIT",
"dependencies": {
"@actual-app/api": "^26.1.0",
"axios": "^1.6.0",
"chalk": "^4.1.2",
"cli-table3": "^0.6.3",
"dotenv": "^16.3.1",
"inquirer": "^8.2.6",
"ora": "^5.4.1"
},
"devDependencies": {
"@types/inquirer": "^9.0.7",
"@types/node": "^20.0.0",
"ts-node": "^10.9.0",
"typescript": "^5.0.0"
}

@ivar2912 commented on GitHub (Jan 16, 2026): As you can see below the correct API version is installed. The same error previously mentioned still persists in actual server. I have no clue what the problem can be. Everything is currently on V26.1.0. /usr/local/lib/node_modules/@lunchflow/actual-flow # cat package.json { "name": "@lunchflow/actual-flow", "version": "0.0.15", "description": "Import transactions from Lunch Flow to Actual Budget with terminal UI.", "main": "./dist/index.js", "bin": { "actual-flow": "./dist/index.js" }, "scripts": { "build": "tsc", "start": "node dist/index.js", "dev": "ts-node src/index.ts", "prepare": "pnpm run build", "install:dev": "pnpm install", "clean": "rm -rf dist", "release:patch": "npm version patch && git push && git push --tags" }, "keywords": [ "lunch-flow", "actual-budget", "importer", "transactions" ], "author": "Amr Awad", "license": "MIT", "dependencies": { **"@actual-app/api": "^26.1.0",** "axios": "^1.6.0", "chalk": "^4.1.2", "cli-table3": "^0.6.3", "dotenv": "^16.3.1", "inquirer": "^8.2.6", "ora": "^5.4.1" }, "devDependencies": { "@types/inquirer": "^9.0.7", "@types/node": "^20.0.0", "ts-node": "^10.9.0", "typescript": "^5.0.0" }
GiteaMirror commented 2026-02-28 20:28:59 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 16, 2026):

Is there any more logs you could share? From both the server (what specific error message is it giving you?) all the way to the UI (what error can you see in developer tools console?).

@MatissJanis commented on GitHub (Jan 16, 2026): Is there any more logs you could share? From both the server (what specific error message is it giving you?) all the way to the UI (what error can you see in developer tools console?).
GiteaMirror commented 2026-02-28 20:29:00 -06:00
Author
Owner
Copy Link

@ivar2912 commented on GitHub (Jan 28, 2026):

Logs: 2026-01-28T18:55:25.100Z info: POST 200 /sync/sync
2026-01-28T18:55:25.437Z info: GET 304 /account/validate

executed: https://actualbudget.org/docs/troubleshooting/server

Docker variable:

  • DEBUG=actual:config,actual-sensitive:config

The result: same issue occures

Image
@ivar2912 commented on GitHub (Jan 28, 2026): Logs: 2026-01-28T18:55:25.100Z info: POST 200 /sync/sync 2026-01-28T18:55:25.437Z info: GET 304 /account/validate executed: https://actualbudget.org/docs/troubleshooting/server Docker variable: - DEBUG=actual:config,actual-sensitive:config The result: same issue occures <img width="1712" height="1276" alt="Image" src="https://github.com/user-attachments/assets/b5355443-3c78-489b-b626-d10693a847ad" />
GiteaMirror commented 2026-02-28 20:29:01 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 28, 2026):

Ok those are server logs and what do you see in the browser console logs?

@MatissJanis commented on GitHub (Jan 28, 2026): Ok those are server logs and what do you see in the browser console logs?
GiteaMirror commented 2026-02-28 20:29:01 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 11, 2026):

This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.

@github-actions[bot] commented on GitHub (Feb 11, 2026): This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bank sync needs info
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#2803
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?