Buffer Not Found

What it means

No buffer in this organization matches the given ID or slug.

This usually points at your integration's setup rather than anything the end user did. Show the end user a generic message like "Something went wrong on our end.", and log detail for your own debugging.

How to fix it

1. 1.

   The value is neither a buffer ID nor a buffer slug, or it names a buffer in a different organization.

   List buffers with GET /api/v0/buffers to get the IDs and slugs for the current organization.

2. 2.

   The buffer was renamed, which changes its slug and retires the old one.

   Address the buffer by its ID, which never changes, or read the new slug from GET /api/v0/buffers.

3. 3.

   The buffer was deleted.

   Fetch the current buffer list again and point routing rules at a buffer that still exists.

Where this happens

• GET/api/v0/feedback· List feedback
• GET/api/v0/buffers/{buffer_id}· Get a buffer
• PATCH/api/v0/buffers/{buffer_id}· Update a buffer
• DELETE/api/v0/buffers/{buffer_id}· Delete a buffer
• GET/api/v0/buffers/{buffer_id}/feedback· List a buffer's feedback
• PUT/api/v0/buffers/{buffer_id}/feedback/{feedback_id}· Add a piece of feedback to a buffer
• DELETE/api/v0/buffers/{buffer_id}/feedback/{feedback_id}· Remove a piece of feedback from a buffer
• POST/api/v0/buffers/{buffer_id}/move-all· Move all feedback to another buffer
• POST/api/v0/routing/test· Test the routing logic
• POST/api/v0/research/queries· Ask a research question