Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Exception] Removed nonexistent document
See original GitHub issue[server-internal] Exception in queued task: Error: Removed nonexistent document 5324TvAxi9MTLsSFS at [object Object]._.extend.removed (packages/ddp-server/livedata_server.js:202:17) at [object Object]._.extend.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Error: Removed nonexistent document · Issue #1629 - GitHub
Issue. Server Setup Information: Operating System:Debian; Deployment Method(snap/sandstorm/mongodb bundle):Snap; Http frontend (Caddy, ...
Read more >Developers - [Exception] Removed nonexistent document -
[server-internal] Exception in queued task: Error: Removed nonexistent document 5324TvAxi9MTLsSFS at [object Object].
Read more >Meteor removing document by ID error - Stack Overflow
I'm trying to remove a single document by its id and I keep getting the following error: Exception in Mongo write: TypeError: object...
Read more >Error 500: HTTP Web Server: Lotus Notes Exception - IBM
Error 500 : HTTP Web Server: Lotus Notes Exception - Invalid or nonexistent document.
Read more >Invalid or nonexistent document
What happened. You tried to select, save, or move a document name that is not valid, in some cases because it does not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@clayne11 I need to reproduce this and I will find a fix. I believe it can be easily solved by interogating the user’s collectionView and check for those docs before calling remove, but then I ask myself, shouldn’t this be default meteor behavior, why did they choose not to do it ?
Created new issue around this.