MongoDB\Driver\Exception\BulkWriteException: Updating the path 'my_collection.updated_at' would create a conflict at 'my_collection'

[rennokki]

MongoDB\Driver\Exception\BulkWriteException: Updating the path 'my_collection.updated_at' would create a conflict at 'my_collection'

This happens in my unit tests after i upgraded to 3.5. This can be simply reproduced:

$model = MyCollectionModel::first();

$model->update($model->toArray());

[rennokki]

This is the stacktrace (the right order is from bottom to top; error occurs on Update.php:179)

vendor/mongodb/mongodb/src/Operation/Update.php:179
vendor/mongodb/mongodb/src/Operation/UpdateMany.php:105
vendor/mongodb/mongodb/src/Collection.php:1008
vendor/jenssegers/mongodb/src/Jenssegers/Mongodb/Collection.php:45
vendor/jenssegers/mongodb/src/Jenssegers/Mongodb/Query/Builder.php:834
vendor/jenssegers/mongodb/src/Jenssegers/Mongodb/Query/Builder.php:591
vendor/jenssegers/mongodb/src/Jenssegers/Mongodb/Eloquent/Builder.php:47
vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php:741
vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php:656
vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php:603
app/Jobs/Soccer/ParsePlayerProfileSchema.php:77

In my job, @ line 77 i have:

$storedPlayer->update($data);

This job also does an API call. The fact is that $data contains the existing Player model as well as some modifications that come from the API call in order to update my stored player with the freshest data, while keeping the other details intact.

Briefly, this line does the same thing as explained before:

$model = MyCollectionModel::first();

$model->update($model->toArray());