Error on one command in a CommandsSubmission batch

As a rule, no.

Most Daml ledger client workflows are well-served by “one at a time” command submissions. If you are truly building a client that benefits from bulk submissions, you should start “thinking in bulk”, i.e. using techniques that are generally useful for bulk data.

The applicable bulk technique that immediately comes to mind is “divide and conquer”. A simple “split in half” resubmission technique can submit 999,999 good commands successfully and find the 1 bad command in only 41 submits using this divide-and-conquer, while not assuming there is only one bad command, so this scales quite well to large numbers of commands, as 1 million is far more than an application ought to consider submitting in one go. A more tailored application can split far more aggressively to avoid waiting for so many aborts.