Error: failed to begin subsegment named 'amazondynamodbv2': segment cannot be found.

Failed to begin subsegment named 'amazondynamodbv2': segment cannot be found means the X-Ray Java SDK tried to trace a DynamoDB call without an active parent segment. It is a tracing-context failure, not a DynamoDB schema error.

1. For incoming HTTP requests, configure the X-Ray servlet filter before code that uses the instrumented client.
2. For startup jobs outside an incoming request, create and close a segment around the work. Keep closure in a finally block.
3. For executor tasks, propagate the current trace entity using the X-Ray context-aware executor or documented thread-context APIs. Reusing a client does not propagate trace context.

AWSXRay.beginSegment("startup");
try {
    // Call the instrumented client here.
} finally {
    AWSXRay.endSegment();
}

This snippet uses the existing X-Ray SDK with com.amazonaws.xray.AWSXRay. Suppressing missing-context errors may hide missing traces; it does not repair propagation. For new instrumentation, AWS recommends migrating from X-Ray SDK instrumentation to OpenTelemetry.

See Java client guidance and AWS documentation.

AWS startup tracing example shows the explicit-segment pattern.