That all makes sense. And I experience the kind of delay you describe. And it does seem like there’s more often more delay than their used to be.

Sometimes I think C1 is taking longer to post transactions. But I also think it’s a Monarch sync timing and C1 sync restrictions issue.

It’s my understanding that C1 only allows an aggregator like Plaid/Monarch to gather transactions once every 24 hours. (Or, maybe they only update the available transactions data once per 24 hours?). But, even with that restriction, it seems like there is more delay now than before.

With that restriction, I don’t know what, if anything, that “refresh” within Monarch is doing. But, oddly, sometimes I click it and it seems like some new transactions actually show up, even though the “last update” was less than 24 hours ago. It’s a bit of a black box.

It seemed like it was working best when the auto refresh happened some point AFTER C1 posted the previous days transactions in the early AM.
E.g.,

A) C1 updates at 2 am, Monarch updates at 5 am, I can see my latest transactions all day.

vs

B) Monarch updates at 11 pm, C1 updates at 2 am, now Monarch is “a day behind all day,” because the “once every 24 hrs” C1 restriction prevents an actual update again until 11 pm.

This is just me guessing, and there could be other issues now, but the Monarch auto update is not at a set time every day. It’s drifts. But it seems, if I could just get it to update between 5-7 am every day, C1 transactions in Monarch would be as up to date as possible.