Bug: SimpleFIN sync issue

[Gamerayers]

How are you using Sure?

Self-hosted on unraid using the 4 different separate apps
Version: [v0.7.2-alpha.7]

Bug description

Sync has errors with datastyle as the reason.

401(K) SAVINGS PLAN (): PG::DatetimeFieldOverflow: ERROR: date/time field value out of range: "1782162576" HINT: Perhaps you need a different "datestyle" setting. CONTEXT: unnamed portal parameter $2 = '...'

Health Savings Account (): PG::DatetimeFieldOverflow: ERROR: date/time field value out of range: "1782188639" HINT: Perhaps you need a different "datestyle" setting. CONTEXT: unnamed portal parameter $6 = '...'

Joint WROS - TOD (): PG::DatetimeFieldOverflow: ERROR: date/time field value out of range: "1782167435" HINT: Perhaps you need a different "datestyle" setting. CONTEXT: unnamed portal parameter $3 = '...'

ALTERNATIVE RETIREMENT PLAN FMTC TRUSTEE (): PG::DatetimeFieldOverflow: ERROR: date/time field value out of range: "1782167435" HINT: Perhaps you need a different "datestyle" setting. CONTEXT: unnamed portal parameter $3 = '...'

PROFIT SHARING/401(K) PLAN AND TRUST (): PG::DatetimeFieldOverflow: ERROR: date/time field value out of range: "1782167435" HINT: Perhaps you need a different "datestyle" setting. CONTEXT: unnamed portal parameter $2 = '...'

There are 91 more of these errors. It is syncing through SimpleFIN and the host for these accounts are Optum Bank and Fidelity.

[dosubot]

This is a known bug where SimpleFIN returns balance-date as a Unix epoch string (e.g., "1782162576") for investment accounts, and that string gets passed directly to PostgreSQL without conversion — causing the PG::DatetimeFieldOverflow error you're seeing.

There's an open PR #2397 that directly fixes this by adding a Simplefin::DateUtils.parse_provider_time() method that detects numeric strings and properly converts them via Time.at() [1]. It hasn't been merged yet, but if you'd like to resolve this immediately, you can apply it locally:

git fetch origin pull/2397/head:pr-2397
git checkout pr-2397

Otherwise, it should land in a future release once reviewed and merged.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.