Error: DynamoDB stream no records processed

“No records processed” can be normal when no eligible changes have arrived. It can also mean a consumer is attached to an old stream, filters discard the events, or processing has stalled. One consumer does not remove records from the stream for another consumer.

1. Check that Streams is enabled and compare LatestStreamArn with the event source mapping. Old mappings do not automatically follow a recreated stream.
2. Make a deliberate change to a test item after the consumer is ready. Rewriting identical data produces no record, and existing table contents are not automatically replayed.
3. Inspect mapping State, LastProcessingResult, FilterCriteria, and starting position. A LATEST mapping reads new traffic, not the retained backlog.
4. Check execution-role stream-read permissions, function concurrency, errors, and IteratorAge. A poison record can repeatedly fail ahead of later records.
5. For a custom reader, continue polling an empty response with NextShardIterator and discover child shards. Stop a closed shard only when its iterator is exhausted.

DynamoDB Streams retains records for 24 hours. Excess readers can cause throttling, but the stream is not a queue where one consumer claims a record exclusively. Use a controlled replay and idempotent handler when recovering a stalled consumer.

See stream consumer behavior and AWS documentation.