Weekly Updates - 2026

2026-05-20

Turnstile follow-up: frontend Sentry errors are much lower, but most of the errors are anonymous. I’ll work with frontend to collect more specific email information for the failed cases to analyze the impact on real users.
For the Morningstar data sharing plan, I’ll work with Kevin to push Morningstar to share the data with us for analysis.

The Morningstar crypto ticker is released on production, Next step I’ll dig more knowledge about Morningstar project prepare for the snowflake data sharing project.
Investigate the data issue about yodlee_account_reference being null. And push forward dirty data cleanup.

The Morningstar crypto ticker is under review. I got some feedback from Tingsong and I’m working on it. I plan to finish an update by end of today and put it on staging tomorrow for product testing.
For the Yodlee dirty loan account cleanup, I’m checking the effort needed to convert these accounts to manual accounts and move the cleanup forward.

Morningstar crypto ticker is now under review.
Pick up a backlog/todo item to work on between reviews currently investigating Redtail OAuth ticket DEV-18463 (transferred from hu.yan)

Crypto project, I have draft the kick-off document, and will be ready for review this afternoon. The kick-off meeting is scheduled for tomorrow.

Yodlee soft refresh refactor project, I have done the firt version of kick-off document, and received some feedback from Tingsong and Monkey. But this plan to pause for now, I turned to work on the crypto project.
Crypto project, I have learned more background and current state of the project, I’ll do some more technical research and api debug to digg more details. And plan to kick-off meeting next week.

Yodlee soft refresh refactor project, I Drafing the kick-off document, and will be ready for review on Friday
Done the impact analysis for Bank of America Open Banking API Migration, receive the confirmed from Yodlee that the account identifiers will not changed, I have replied to Megan.

Follow up on 4 action items from data issue investigation synced with Tingsong last week, new data issue tickets forking out additional items
Yodlee soft refresh optimization: exploring Saloon refactoring for API and notification, planning to discuss with Tingsong on Friday about

Yodlee BOA Open Banking API Migration: After investigation, we confirmed that RightCapital is not impacted by the upcoming BOA API migration, as we do not use the affected Sync Data Extracts API or FastLink Deep Link Flow. No engineering changes are needed on our side.
Clean up Yodlee dirty loan account data: Left a new comment to Megan for proposal of cleanup approach, waiting for confirmation.
Initial sync with Tingsong on 4 action items forked from data issue investigation
Yodlee soft refresh optimization: Preparing the kick-off documentation and discussion for the project.

The main thread of my work is: Yodlee soft refresh optimization。Tingsong shared more details about the roadmap and direction. Next step is to prepare the kick-off documentation and dissussion
Clean up Yodlee dirty loan accounts — left a comment to Megan for confirmation before cleanup
- The cleanup hotfix will be ready for review today or tomorrow
Investigate positions.custom_security.type being null

Working on investigate several data issue tickets
Turnstile plan to test on staging with frontend
Yodlee soft refresh optimization, I digged more about the data flow and architecture of the current state.

Yodlee soft refresh optimization - still working on the kick-off document, debugged data flow via DAG Sites, will discuss technical details and solution with Tingsong after the holiday
Turnstile - planning testing on staging, today or tomorrow

Yodlee soft refresh optimization, Tingsong aligned with me the main goal of this project is put soft-refresh logic into a asynchronous job with server-push status & notifications to improve user experience. and also refactor connector to use saloon. Currently I getting start the background knowledge and prepare the kick-off documentation.

Turnstile development is ongoing. The backend develop work is almost done; the frontend is still in progress. I’ll be pushing forward with review and testing.
Regarding the Salesforce My Domain endpoint: Thea confirmed with Salesforce that this was a temporary workaround. Therefore, we’re not switch to the My Domain endpoint approach. Based on my observations from last night through today, the original test.salesforce.com endpoint has returned to normal. We also don’t plan to proceed with the OAuth grant type changes at this stage, as we’re planning to reduce retail’s direct dependency on Salesforce. The path forward is to route Salesforce API calls through platform instead, so the OAuth can be handled on the platform side.

Turnstile’s kick-off meeting scheduled for tomorrow. I have offline discussions with frontend about the details about fallback plan.
Household TCM bug fix PR is merged, while fixing the model refresh function need to rethink whether our custom implementation is still worth keeping.
Salesforce package testing is failing. Right now, we’re just skipping it. We need to change the OAuth settings (endpoint and grant type). I plan do it this week to remove the todo and catch up with the next release.

I keep working on the Turnstile development. The frontend dev, gaogao, is on vacation, so I’ve aligned with Alex to move the kickoff plan to next week when gaogao is back. That pushes the release back one more cycle past the original January 13 plan.
Fixing a bug where household restrictions when transferring advisor from firm, the household’s TCM were not properly updated. The PR is ready for review.
About the big monorepo project, I’m preparing a doc to summarize what I’ve tried so far, to discuss and align on the goals.