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

[PR #6621] [WIP] Fix syncing error in Actual during transaction import #6633

New Issue
Closed
opened 2026-02-28 21:30:54 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:30:54 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/6621

State: closed
Merged: No

Investigation and Plan for Syncing Error Issue

  • Understand the issue - users importing transactions via third-party tools (Lunchflow) see generic sync error
  • Locate error message source - found in packages/desktop-client/src/sync-events.ts line 365
  • Trace sync error handling - found catch-all error handler in packages/loot-core/src/server/sync/index.ts line 604-608
  • Improve error logging and capture more error details in sync catch-all handler
  • Add better error context to help debug sync failures
  • Test the changes to ensure error details are properly captured and logged
  • Run type checking and linting
  • Document changes
Original prompt

This section details on the original issue you should resolve

<issue_title>[Bug]: synching error actual</issue_title>
<issue_description>### 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</issue_description>

Comments on the Issue (you are @copilot in this section)

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

**Original Pull Request:** https://github.com/actualbudget/actual/pull/6621 **State:** closed **Merged:** No --- ## Investigation and Plan for Syncing Error Issue - [x] Understand the issue - users importing transactions via third-party tools (Lunchflow) see generic sync error - [x] Locate error message source - found in `packages/desktop-client/src/sync-events.ts` line 365 - [x] Trace sync error handling - found catch-all error handler in `packages/loot-core/src/server/sync/index.ts` line 604-608 - [x] Improve error logging and capture more error details in sync catch-all handler - [x] Add better error context to help debug sync failures - [x] Test the changes to ensure error details are properly captured and logged - [x] Run type checking and linting - [x] Document changes <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>[Bug]: synching error actual</issue_title> > <issue_description>### 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</issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > </comments> > </details> <!-- START COPILOT CODING AGENT SUFFIX --> - Fixes actualbudget/actual#6619 <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).
GiteaMirror added the pull-request label 2026-02-28 21:30:54 -06:00
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 pull-request
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#6633
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?