API exception if transaction is deleted by rule

[Medformatik]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem
• ... it's definitely a Firefly III issue, not me

Description

The issue has already been reported in #5177 but it hasn't been fixed. If there is a rule that deletes transactions created by the API or the data importer in certain cases (in my case, if it has the tag pending), an error is triggered (as described in the issue).

200032: Cannot find transaction. Possibly, a rule deleted this transaction after its creation.

This is understandable so far, but in this case the deletion is intended. Therefore, I don't want to receive an email with such an error every time.

Debug information

Debug information generated at 2024-03-12 08:32:57 for Firefly III version v6.1.10.

System information
Item	Value
Firefly III	6.1.10 / v2.0.12 / 22 (exp. 22)
PHP version	8.3.3 (64bits) / apache2handler / Linux x86_64
BCscale	12
Error reporting	Display: Off, reporting: ALL errors
Max upload	67108864 (64 MB)
Database drivers	*mysql*, pgsql, sqlite,
Docker build	#1003, base #81

Firefly III information
Item	Value
Timezone	Europe/Berlin + Europe/Berlin
App environment	local, debug: false
Layout	v1
Logging	notice, stack / (empty)
Cache driver	file
Default language and locale	de_DE + equal
Trusted proxies	**
Login provider & user guard	eloquent / web
Login headers	N/A + N/A
Stateful domains
Last cron job	2024-03-12 00:00:00 (8 hours ago)
Mailer	smtp

User-specific information
Item	Value
User	#1 of 1
User flags	🔧
Session start
Session end
View range	1M
User language	de_DE
User locale	de_DE
Locale(s) supported	de_DE.utf8: ✅ de_DE.UTF-8: ✅
User agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:123.0) Gecko/20100101 Firefox/123.0

Expected behaviour

It would be great if you could set how this case is handled. I want the deletion so that the import only happens when the booking is no longer pending. Therefore, I don't care about the error and I don't need to receive any emails about it.

Steps to reproduce

1. Create a rule which deletes a transaction on creation
2. Create a transaction via API or data importer which is covered by this rule

Additional info

No response

[JC5]

Sorry, since this could also be an indication of other problems I'm not planning to change this behavior.

[Medformatik]

Wouldn't it be an idea to be able to set that the error is ignored (not by default, of course) or at least that no email is sent for it?
Or an API parameter with which you can specify that such an error should be ignored (and then a corresponding option in the data importer).
Or is your recommendation simply to turn off the error emails completely? I have to deal with it somehow.

[JC5]

I'll see what I can do.

[github-actions]

Hi there!

This is an automatic reply. Share and enjoy

This issue has been marked as an enhancement. The requested enhancement to an existing feature will become a part of Firefly III or the data importer in due course.

If you come across this issue, please be aware there is NO need to reply with "+1" or "me too" or "I need this too" or whatever. Such comments are not helpful, and do not influence the roadmap. Your comment may be 💀 deleted. You can subscribe to this issue to get updates.

Thank you for your contributions.