James Cole

And it's in place!

The base image is public on Azure: https://dev.azure.com/Firefly-III/_git/BaseImage Specifically: https://dev.azure.com/Firefly-III/_git/BaseImage?path=/apache-8.2 Whatever works for you works for me, I'm happy to merge things!

I'm getting daily errors now about the secondary rate limit.

It stopped being an issue for me when I spaced out other recurring actions. So not all actions at exactly midnight. Those other actions were also influencing the rate limit....

Indeed, the amount is calculated so it's not readily available. I'll see what I can do. It's on the list!

I'll put it on the list!

It requires significant database changes if you want to do this right. So no. I have other priorities right now.

That's not simple, it requires at least a jump to 6.2.x and there are plenty of other places where piggy banks are used. Feel free to fork the code though...

No, sorry. This can be done using webhooks if you want, but you'll have to develop something yourself to translate between Firefly III data and Slack data.

I'm not sure which old days you refer to, but if both the IBAN and the account number are present, the IBAN will always take precedence.