invalid_cursor

HTTP status: 400 · Code: invalid_cursor

A pagination cursor the server can’t read.

Why it happens

A list call got a cursor the server can’t read. Cursors are opaque: one that was edited, cut short, or taken from a different list fails.

How to fix

Pass back exactly the nextCursor the previous page returned, or use the SDK’s listAll helper, which pages for you. To start over, leave the cursor out.

Catch it in your code

Every SDK throws one error type for a failed call. Match on its code, which is always invalid_cursor for this error, never on the message.

JavaScript and Next.js

import { ErrorCode, OrvanoError } from '@orvano/js'

try {
  // your Orvano call
} catch (error) {
  if (error instanceof OrvanoError && error.code === ErrorCode.invalidCursor) {
    // handle invalid_cursor
  } else {
    throw error
  }
}

Dart and Flutter

import 'package:orvano_flutter/orvano_flutter.dart'; // or orvano_dart on a server

try {
  // your Orvano call
} on OrvanoException catch (error) {
  if (error.code != ErrorCode.invalidCursor) rethrow;
  // handle invalid_cursor
}

.NET

using Orvano;

try
{
    // your Orvano call
}
catch (OrvanoException error) when (error.Code == ErrorCode.InvalidCursor)
{
    // handle invalid_cursor
}

The error also carries the HTTP status (400), a message, and a request ID. Quote the request ID when you report a problem: the server logs it with the failure. See Errors for how errors work in every SDK, or every error code.