
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
- Is my approach for deleting registered u...
A few weeks ago, I was advised not to use the registered users' id in my web app. Instead, I store the publicly viewable information such as username and email ...
- Stuck in "deleting"
my parent element have relationship that doesnt exist and its stuck in "deleting", i cant delete it gives me error: Collection with the requested ID could not b...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
