clean up corrupt file

  • 1
  • Problem
  • Updated 3 months ago
I have started using Goodbudget again as a serious alternative to Quicken. I was a couple of weeks from pulling the trigger to be a paying member when problems appeared. I believe they started after I deleted some envelope transfers, but I can't be sure. My file is corrupt for unknown reasons.
Perhaps the large gaps in my transactions, the envelope transfers - who knows. The point is the little meter bar/slider hash on the envelope is incorrectly showing where I am in my budget cycle and the spending to budget report only shows the same (incorrect) spending amount regardless of the number of budget periods selected. This may be because I intuitively used Goodbudget for many years, not taking into account its bugs and quirks reported in this forum. I am going to take one more stab at cleaning it up before moving on to another app.

I am looking for help in flushing the account of old transactions and reloading the latest 104 transactions;
1) The batch delete does not work. Select all (1817) old and the delete option is greyed out
2) Cannot delete all transactions and reload from my exported CSV without recategorizing

If I have to start over, it seems I would be better off using an app without the functionality limitations. Please help.
Photo of Mike Alleman

Mike Alleman

  • 9 Posts
  • 0 Reply Likes
  • resigned to defeat

Posted 3 months ago

  • 1
Photo of Alex Park

Alex Park, Official Rep

  • 209 Posts
  • 42 Reply Likes
Hi Mike,

Sorry to hear about the myriad of troubles you've been experiencing with Goodbudget. Would you be able to send us an email at support@goodbudget.com with your Goodbudget household email address so we can take a closer look at your household? Seeing your household and being able to see what you're seeing should put us in a better position to help you and answer your questions.
Photo of Mike Alleman

Mike Alleman

  • 9 Posts
  • 0 Reply Likes
Thanks for your help Alex. I have sent my info. I would like to tell the users in this forum that the issue only exists on the desktop web interface. My phone is reporting correctly.