Skip to main content

NS Does Not Exist Error

NS does not exist error.

Praise Magidi avatar
Written by Praise Magidi
Updated yesterday

Step

Buffer

Message

`ns does not exist: buffer.buffer668e73fd60d1930959722fb9`

Cause

This error is caused by attempting to read or write to a buffer collection that has just been purged.

Resolution

If there are flows or steps purging the buffer, allow for sometime before attempting to read or insert records. You can also re-run the flow, as the buffer collection will most likely be done by recreating.

Error Detail

json
{
"error": {
"errmsg": "ns does not exist: buffer.buffer668e73fd60d1930959722fb9",
"code": 26
"codeName": "NameSpaceNotFound"
},
"message": "ns does not exist: buffer.buffer668e73fd60d1930959722fb9",
"errorMessage": null,
"invalid" : null
"stepType" : null
"stepName" : null
"title" : null
}

Did this answer your question?