🐛 Bug Report: databases.deleteDocuments() doesn't execute events

[ArielS1]

👟 Reproduction steps

I have a function that listens to the following event:
databases.main.collections.myCollection.documents.*.delete

When i delete a myCollection document using databases.deleteDocument() it executes the function as it should.
But when i delete it using the experimental function databases.deleteDocuments() it doesn't, even that the document was deleted successfully, it happens even when a single document is deleted.

I suspect such problem might happen in other bulk DML operations too on their relevant events.

👍 Expected behavior

to execute the function that listens to databases.main.collections.myCollection.documents.*.delete event

👎 Actual Behavior

file deleted, function wasn't executed

🎲 Appwrite version

Different version (specify in environment)

💻 Operating system

Linux

🧱 Your Environment

Appwrite 1.7.4 self hosted
node sdk 17.1.0
runtime node-22

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[ArielS1]

I found out that the problem is not consistent with another collection.
On that collection I have a bulk delete that does execute the function that listens to the delete event
The events are defined in the same way on both of listening functions in the same way, only a different collection name
In both of them there is a single query condition on an indexed (key) required field field

Only in one of them the bulk delete doesn't invoke the listening function, but a single delete does without changing the listening function.

[ArielS1]

As a workaround for this problem i tried to start managing the file deletions by using relations between collections with a cascade deletion rule and i noticed that when a file is deleted because of the cascade (deleted the parent object) then it also doesn't invoke the child's delete event and the function that listens to it doesn't invoke.

I suspect the reason is because under the hood the cascade deletion is using the bulk deleteDocuments() method and then it reproduces the problem i described in this issue.