findByIdAndDelete not finding the provided id - node.js

Question

I am trying to use Mongoose findByIdAndDelete() method on a model but it does not see the _id it needs to delete.
My route is declared similar to this (minified) example:
router.delete('/delete-entity/:id', (req, res) => {
Entity.findByIdAndDelete(req.params.id)
.exec()
.then((docs) => { ...handle success })
.catch((err) => { ...handle error });
});
I only have middleware running that hooks into the save method of the model. But this middleware does not touch the _id field.
When I console.log() inside the route I can see that req.params.id is set. Also if I try to identify my document using an other field to delete it (so not the _id field), it does works. However when I try to use the _id field all that is returned to the client is ''. This makes me believe that something goes wrong in comparing datatypes of the _id field. But cating using mongoose.Type.ObjectId() did not help either.
What could be going on here?
In addition to this already provided information. Here is my model.
const embeddedEntity = new mongoose.Schema({
name: { type: String, required: true }
}, { _id: false });
const entity = new mongoose.Schema({
name: { type: String, required: true },
embeddedInfo: { type: embeddedEntity, required: true }
});
module.exports = mongoose.model('Entity', entity);
#Invider I managed to get this from the profiler.
{
"op" : "command",
"ns" : "development.entities",
"command" : {
"findAndModify" : "entities",
"query" : {
"_id" : ObjectId("5dc95b8cc472d31232dba5a3")
},
"new" : false,
"remove" : true,
"upsert" : false,
"lsid" : {
"id" : UUID("30086660-0619-440e-9268-148957428a2b")
},
"$db" : "development"
},
"keysExamined" : 0,
"docsExamined" : 0,
"ndeleted" : 0,
"numYield" : 0,
"locks" : {
"Global" : {
"acquireCount" : {
"r" : NumberLong(1),
"w" : NumberLong(1)
}
},
"Database" : {
"acquireCount" : {
"w" : NumberLong(1)
}
},
"Collection" : {
"acquireCount" : {
"w" : NumberLong(1)
}
}
},
"responseLength" : 74,
"protocol" : "op_msg",
"millis" : 0,
"planSummary" : "IDHACK",
"execStats" : {
"stage" : "DELETE",
"nReturned" : 0,
"executionTimeMillisEstimate" : 0,
"works" : 1,
"advanced" : 0,
"needTime" : 0,
"needYield" : 0,
"saveState" : 0,
"restoreState" : 0,
"isEOF" : 1,
"invalidates" : 0,
"nWouldDelete" : 0,
"nInvalidateSkips" : 0,
"inputStage" : {
"stage" : "IDHACK",
"nReturned" : 0,
"executionTimeMillisEstimate" : 0,
"works" : 1,
"advanced" : 0,
"needTime" : 0,
"needYield" : 0,
"saveState" : 0,
"restoreState" : 0,
"isEOF" : 1,
"invalidates" : 0,
"keysExamined" : 0,
"docsExamined" : 0
}
},
"ts" : ISODate("2019-11-14T09:27:52.988Z"),
"client" : "127.0.0.1",
"allUsers" : [ ],
"user" : ""
}

Answer 1

A lot of thanks goes out to #invider and #SuleymanSah for pointing me into the right direction.
The problem was actually something pretty simple that I completely overlooked and was indeed related to the datatype as I expected.
My e2e tests were failing because of the same problem as trying to call the route using Postman.
The problem was that when adding test samples to the database I was setting the _id field myself. This most likely causes the value stored to be of type string. Letting MongoDB itself set the _id field solved this issue. At least for working in the live environment using Postman.
For my e2e test I had to modify my the data that will be loaded into the database for each test. I was adding samples in the following way:
{
_id: '5dc95b8cc472d31232dba5a5',
name: 'SomeData',
embeddedInfo: {
name: 'someOtherData'
}
}
I should have casted the _id into an ObjectId first. Like so:
{
_id: mongoose.Types.ObjectId('5dc95b8cc472d31232dba5a5'),
name: 'SomeData',
embeddedInfo: {
name: 'someOtherData'
}
}
Again. Thanks to the both of you.