Bug: Manual Sync has vanished, Transactions not contributing to balances

[steveredden]

Before you start (required)

General checklist

• I have removed personal / sensitive data from screenshots and logs
• I have searched existing issues and discussions to ensure this is not a duplicate issue

How are you using Maybe?

• I am a paying Maybe customer (hosted version)
  • Paying Maybe users can also open requests in Intercom (if there is sensitive info involved)
• I am a self-hosted user

Self hoster checklist

Paying, hosted users should delete this entire section.

If you are a self-hosted user, please complete all of the information below. Issues with incomplete information will be marked as Needs Info to help our small team prioritize bug fixes.

• Self hosted app commit SHA (find in user menu): 9e6b4b1
  • I have confirmed that my app's commit is the latest version of Maybe
• Where are you hosting?
  • Render
  • Docker Compose
  • Umbrel
  • Other (please specify)

---

Bug description

Looks like going from digest:88fb255edad8c55447b35ebdce96170d9a5ee0579d85f6a41db5e67558ceb1c5
to digest: ff1351f88b9f7b4d65d639ae59f65489b9fb28c4612a71cb85a7696676ba676a

removes the manual sync button

before:

This causes transactions that get imported to not update balances:

Clicking sync (on the old version) did cause the transactions to refresh (after sync + browser refresh):

Where did the button go? will it come back? any way to manually refresh now?

[steveredden]

9e6e4b1

[steveredden]

seems like the only way to trigger an update is to disable and enable the account?

[electricmessiah]

Known issue, but just to throw in, enable/disable the account still causes "syncing" message that never goes away and adds yet another "pending sync" entry to the syncs table in the db.

[nikhilbadyal]

Not sure what's the reason to remove sync-all button. It was not causing any harm(I hope). I see lot of earlier features are gone, not sure for what reason.
Eg. - Earlier, below button used to open import menu directly with current account pre-selected. Now it just opens the import settings and we have to click New Import and then few more clicks to get things done.

[Joelute]

The removal of the sync button has been provided in #2236.

[steveredden]

https://github.com/steveredden/simplefin_to_maybe/blob/main/docs/manual_sync.md

docker exec -it $(docker ps --filter "name=maybe-app" --format "{{.ID}}" | head -n1) bash -c "bundle exec rails runner 'Family.find_each { |family| family.sync_later(window_start_date: 1.day.ago, window_end_date: Time.current) }'"

[javiermartingonzalez]

Thank you @steveredden it was usefull for me!!

Something was broken in a commit between 5125411 and the latest one and autosync is not working and needed to force it.

However, I rolled back to 5125411 (no db migrations was made) and after rolling back, autosync is working again...

Please Maybe @zachgoll , allow us a manual sync button to launch the process in cases where the auto sync failed (today I'm able to perform a rollback but if something is broken and is not possible to roll back, the app won't sync...)

[nikhilbadyal]

Manual sync, if not feasible in the hosted instance due to performance issues, should at least be available in self-hosted instances.

[zachgoll]

@javiermartingonzalez @nikhilbadyal I've added back the manual sync for accounts in the self hosted version:

4044a85

That said, I want to outline our longer term approach to this for additional context:

• Long term, users should not have to think about "syncing". The app should "just work". That is the original motivation for removing these.
• Right now, we're working through some data syncing issues and scaling issues (hosted version), so once we fix those, our "just work" philosophy will be a bit more truthful :) There's just a lot of edge cases to cover.
• We're also working towards partial syncs, as outlined in perf(syncs): implement partial idempotent syncs interface #2309. This will make each sync a lot less intrusive.
• Finally, I'll be pushing some changes around the UI / UX of syncs. Right now, it's completely blocking, which is causing trouble for some users in Bug: The loading of the global synthesis and each asset is very long #2305. Most of these issues on self-hosted instances are a result of an invalid Redis setup, but still, I think the sync states need to be less intrusive and we load the data we have while things are syncing.

Hopefully that clarifies a few things!