Hi Bruce,
I am not aware of any maximum number of burnup steps in TRITON. If there is, we should catch it at the time of the input processing. Can you post the error message you are seeing?
A possible explanation of this behavior could be that you are running out of memory. Is it possible to re-run the case and observe the memory footprint during the steps before it stops?
Could you otherwise post your input file?
Thanks,
Rike