github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-20 22:21:38 -05:00
Code Issues 2.1k Packages Projects Releases 57 Wiki Activity

[GH-ISSUE #7710] [Bug]: Unexpected error on 26.5.0 update [Exception] Error: no such column: _.custom_upcoming_length #80609

New Issue
Open
opened 2026-05-19 04:26:20 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-05-19 04:26:20 -05:00
Owner
Copy Link

Originally created by @EwenQuim on GitHub (May 4, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7710

What happened?

Updating the app from 26.4.0 to 26.5.0, I get this error on Arc (Chrome) and Zen (Firefox) on all pages, on loop (not infinite loop, just repeated ~5 times).

Image Image Image

Also, the list of transactions is now empty.

Image

How can we reproduce the issue?

  • Update to 26.5.0 from 26.4.0
  • Go to any page to view the popup error message
  • Go to the transations (/accounts/:id) to view that the transactions list is now empty

All the advanced/experimental settings were left disabled.
OpenID is enabled.
A few split transactions exist.
The error happen even after server and browser restart.
I cannot go back to 26.4.0, the software tells me the budget file is now only editable on version 26.5.0.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Chrome

Operating System

Mac OSX

Originally created by @EwenQuim on GitHub (May 4, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7710 ### What happened? Updating the app from 26.4.0 to 26.5.0, I get this error on **Arc (Chrome) and Zen (Firefox)** on all pages, on loop (not infinite loop, just repeated ~5 times). <img width="414" height="141" alt="Image" src="https://github.com/user-attachments/assets/6bfe548a-4b43-4959-8626-0a100f376c11" /> <img width="545" height="908" alt="Image" src="https://github.com/user-attachments/assets/42694562-e390-4555-b30e-2cd85fc3b58c" /> <img width="654" height="615" alt="Image" src="https://github.com/user-attachments/assets/969bc5a7-3895-4217-a123-c07bb4580fd0" /> Also, the list of transactions is now empty. <img width="1200" height="1046" alt="Image" src="https://github.com/user-attachments/assets/9a772038-9c93-4652-9e76-7dc035a6da04" /> ### How can we reproduce the issue? - Update to 26.5.0 from 26.4.0 - Go to any page to view the popup error message - Go to the transations (`/accounts/:id`) to view that the transactions list is now empty All the advanced/experimental settings were left disabled. OpenID is enabled. A few split transactions exist. The error happen even after server and browser restart. I cannot go back to 26.4.0, the software tells me the budget file is now only editable on version 26.5.0. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox, Chrome ### Operating System Mac OSX
GiteaMirror added the bugneeds info labels 2026-05-19 04:26:23 -05:00
GiteaMirror commented 2026-05-19 04:26:24 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (May 4, 2026):

Do your browser clients report being on version 26.5? That looks like a version mismatch error.

<!-- gh-comment-id:4372998891 --> @youngcw commented on GitHub (May 4, 2026): Do your browser clients report being on version 26.5? That looks like a version mismatch error.
GiteaMirror commented 2026-05-19 04:26:24 -05:00
Author
Owner
Copy Link

@EwenQuim commented on GitHub (May 4, 2026):

Yes it is on 26.5.0 indeed, why do you think it is a version mismatch ?

It also happen on private window when connecting and refetching my data from 0.

<!-- gh-comment-id:4373005031 --> @EwenQuim commented on GitHub (May 4, 2026): Yes it is on 26.5.0 indeed, why do you think it is a version mismatch ? It also happen on private window when connecting and refetching my data from 0.
GiteaMirror commented 2026-05-19 04:26:25 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (May 4, 2026):

Because that error looks like a db migration error.

<!-- gh-comment-id:4373069934 --> @youngcw commented on GitHub (May 4, 2026): Because that error looks like a db migration error.
GiteaMirror commented 2026-05-19 04:26:26 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (May 4, 2026):

If you access your budget in an incognito window does it still give the same error?

<!-- gh-comment-id:4373072193 --> @youngcw commented on GitHub (May 4, 2026): If you access your budget in an incognito window does it still give the same error?
GiteaMirror commented 2026-05-19 04:26:26 -05:00
Author
Owner
Copy Link

@EwenQuim commented on GitHub (May 4, 2026):

Yes it does

<!-- gh-comment-id:4373506993 --> @EwenQuim commented on GitHub (May 4, 2026): Yes it does
GiteaMirror commented 2026-05-19 04:26:27 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (May 4, 2026):

Thats strange. Can you export your budget file? If you can, then open the sqlite db inside and see if the schedules table has a custom_upcoming_length column.

<!-- gh-comment-id:4373623547 --> @youngcw commented on GitHub (May 4, 2026): Thats strange. Can you export your budget file? If you can, then open the sqlite db inside and see if the schedules table has a custom_upcoming_length column.
GiteaMirror commented 2026-05-19 04:26:27 -05:00
Author
Owner
Copy Link

@EwenQuim commented on GitHub (May 4, 2026):

I prefer debug it myself as it contains my bank info. It seems that the table schedules does not contains this column custom_upcoming_length

<!-- gh-comment-id:4373692596 --> @EwenQuim commented on GitHub (May 4, 2026): I prefer debug it myself as it contains my bank info. It seems that the table schedules does not contains this column `custom_upcoming_length`
GiteaMirror commented 2026-05-19 04:26:28 -05:00
Author
Owner
Copy Link

@EwenQuim commented on GitHub (May 4, 2026):

I'll investigate this bug myself, I'll keep you updated next week.

Thanks a lot for your help though @youngcw !

<!-- gh-comment-id:4373707236 --> @EwenQuim commented on GitHub (May 4, 2026): I'll investigate this bug myself, I'll keep you updated next week. Thanks a lot for your help though @youngcw !
GiteaMirror commented 2026-05-19 04:26:28 -05:00
Author
Owner
Copy Link

@jrhedman commented on GitHub (May 7, 2026):

@EwenQuim In your browser, click on your budget name -> switch file, and then delete the local file only.

Then pull / redownload the file from the server again.

That should fix the migration/sync issue.

<!-- gh-comment-id:4393149798 --> @jrhedman commented on GitHub (May 7, 2026): @EwenQuim In your browser, click on your budget name -> switch file, and then delete the **local file only**. Then pull / redownload the file from the server again. That should fix the migration/sync issue.
GiteaMirror commented 2026-05-19 04:26:28 -05:00
Author
Owner
Copy Link

@jmckarvel commented on GitHub (May 8, 2026):

@jrhedman I was having the same issue and this worked for me. I also had to clear cookies and site data.

<!-- gh-comment-id:4405968751 --> @jmckarvel commented on GitHub (May 8, 2026): @jrhedman I was having the same issue and this worked for me. I also had to clear cookies and site data.
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 bug 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#80609
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?