gavin/maybe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

Propagate child sync errors up to parent, fix sync status #2232

Merged
zachgoll merged 2 commits from zachgoll/mark-parent-sync-failures into main 2025-05-10 02:56:49 +08:00
Conversation 0 Commits 2 Files Changed 9 +29 -22
zachgoll commented 2025-05-10 02:46:49 +08:00 (Migrated from github.com)
Copy Link

Previously, if a child sync failed, it was not propagating that error status upwards to the parent.

This caused odd behavior in the UI where a single account sync within a Plaid item would fail, but the Plaid Item would report "synced successfully" in the UI giving the user no indication that something was wrong.

Previously, if a child sync failed, it was not propagating that error status upwards to the parent. This caused odd behavior in the UI where a single account sync within a Plaid item would fail, but the Plaid Item would report "synced successfully" in the UI giving the user no indication that something was wrong.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
📆 Planned
Not ready to be worked on yet, but planned for future
 💻 Self Hosted only
Issues pertaining to self-hosted versions of Maybe
 ⚙️ Config
ℹ️ Needs info
Further information is requested
 📱 Mobile
Bugs exclusively happening on mobile devices
 1️⃣ High Priority
High priority issues will be worked on next
 🚨 Urgent
Issues that are urgent for app functionality
 3️⃣ Low priority
Contributions accepted, but Maybe team will not be working on this in the near term
 2️⃣ Medium Priority
Community contributions accepted, Maybe team only works on if there are no high priority items open
 ⚡ Performance
Performance issues to address
 🎨 UI / UX
Issues related to UI / UX interactions and design.
 💎 Bounty
💰 Rewarded
📊 Data issue
Issues where the app functionally works, but the data is missing or inaccurate.
 🙋 Bounty claim
$1.5K
Community
This is a great issue for community members to work on
 dependencies
Pull requests that update a dependency file
 Design
Hosted only
Hosted app only
 Required self hoster data migration
Self hosters must run data migrations to resolve this issue
 ruby
Pull requests that update Ruby code
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gavin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gavin/maybe#2232
Delete Branch "zachgoll/mark-parent-sync-failures"

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?