When testing performance, I created a PCAP infoset with thousands of packets in it. To avoid printing it all out, I made the PCAP data be in a hidden group, and had another element with an inputValueCalc expression reach into the PCAP packets to spot check a value in there.

I found that if you try to index farther than element 2263 it fails.

See testBinaryLongRunningForProfiling in daffodil-perf to reproduce. The schema it uses has 2263 wired into it for now.