The x-appwrite-user-id header in the request seems to contain an ID (...7f28) different from the user document ID (...2e4b) in the users collection. It looks like the x-appwrite-user-id is not the user document ID that I'm trying to delete.
Given the event is users.truncatedfordemo2e4b.delete, I might be able to extract the user ID from the x-appwrite-event header instead to get the correct ID (...2e4b) of the document to delete.
Is this a bug?
[Functions] x-appwrite-user-id different from actual user.$id as per the event
Perhaps because I'm deleting the user document myself in the dashboard...
Then it would be a different user correct?
Yes it is probably that
If you're deleting via the console, you're deleting as your console user so it will be the id of your console user
Btw, the body of an execution triggered by an event should contain the related payload. So in your case, it should be the deleted document
Recommended threads
- Why does this happen?
`AppwriteException: general_argument_invalid, Invalid `secret` param: Value must be a valid string and at least 1 chars and no longer than 256 chars (400)` the...
- How to properly implement custom domain?...
- Site deployment does not work.
I can change a file, deploy, change does not take effect. Delete file in repo, push changes,deploy. Old file remains undeleted Duplicate file, rename it, push,...