The thing that I am keen on is galvanising momentum towards a fix, whenever Monzo wake up to this (not for me, mine won’t fire for another month, but a lot of other people will be affected within that tiemframe). “Sorry, it’s not a bug” and a “timing tweak” belie the fact that is is actually a critical issue for this particular feature, in a critical class of actions within Monzo - payments. For a bank, in the scale of things, few bugs are above “my payments all failed”.
In the (some large) startups I’ve worked in, if this sort of bug came up it would be a you’re-working-this-weekend type of fix! So, what I am trying to say is that although this feature isn’t being used by all customers, whatever subset are using it - and more will try, and fail, every day - erodes their confidence in the product. So it should be fixed, ASAP, as a critical bug.
Hopefully someone from Monzo will catch its soon. Though of course it would be helpful if someone from the coral crew flagged it sooner…
They aren’t paid or employed by Monzo. They have their own opinions and ideas. They are (rightly) held to a high standard of behaviour such as treating people fairly. (I don’t think it covers disagreements over whether something is a bug or not, or reporting individual customers’ concerns, though! )
This comes up from time to time and must be incredibly wearing for the Crew, who, after all, are just volunteers and folk that like to hang out here…
Last thoughts on the subject as we’re way off topic:
Each person responds differently. For me, I think that I’d grow tired having to continually defend myself from inaccurate assumptions.
Yes, that what the code of conduct says.
Absolutely not! Everyone has different opinions, and the Coral Crew are entitled to theirs - which may or may not be the same as each other or with Monzo. To that point, I’ve seen members of the Crew (politely) disagree with each other and with Monzo. Constructive feedback, including from the Crew, is welcome here.
Someone from the relevant team will be along shortly, but I can confirm this is a known bug
Scheduled withdrawals currently run at the same time as standing orders, because they’re part of the same system. Ideally these would be split up. As we add more features, it’s going to get increasingly hard to schedule them all in the right order!
As a bit of trivia, I believe the Bacs runs are defined in BST, but the scheduled payment run is defined in UTC. So the order will change when daylight savings kicks in…
Well it’s a good job there’s been an announcement to abolish daylight savings time changes hahaha! It was funny how I’d get a message from all legacy banks saying that I couldn’t use cash machines overnight when the clocks change. I can only assume that they’re remote desktoping into each cash machine and changing the time on them
Well, early this morning my rent and Limitless payments went out. I got a notification while I was sleeping saying I’m now overdrawn (but by the time I woke up I wasn’t because my pot withdrawals happened as well). I would appreciate a re-timing of these things if only to not have notifications saying I’m overdrawn when the server already knows I’m going to pay for it an hour or so later.