[Bug]: Auto-generated schedules don't seem to work with new transactions

[mullermn]

Verified issue does not already exist?

• I have searched and found no existing issue
• I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

I have recently moved to Actual from YNAB4 and done an import of that budget. I used the autodiscovery of schedules feature and set up a load of rules. I've then set up GoCardless and started receiving live transactions, but they never seem to match automatically.

I have been through these very carefully (and it's many rules, not a single rule) and I've checked every single field, and also messed around with the fields to try and make them more tolerant to get a match, but I cannot get it to work. It's like there's some hidden attribute in the auto generated schedule that is being compared and preventing a match.

And here's the new transaction that should have matched:

When I create a new schedule based on the current transaction, it doesn't match the pre-Actual ones either. I backedated the one in this screenshot to August and it hasn't matched August or September.

These Tesla payments happen to be almost perfectly consistent in date/amount etc so there is no (logical) reason why they wouldn't all match, unless the rule is incorporating baggage that it imported from YNAB in its matching logic behind the scenes?

At least one other user thinks they are experiencing this:
https://discord.com/channels/937901803608096828/1291668861233659904

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Safari, Desktop App (Electron)

Operating System

Mac OSX