As described in T308171 and T311519, template errors are causing translation to fail altogether, instead of proceeding with the following template on the queue.
Consider marking templates as non-applicable in these cases.
However, including the error somewhere in the template output would be useful to diagnose the problem from the Web2Cit-Server debugging information, or from the Web2Cit-Editor, which already includes in its data model a place to store such errors.
including the error somewhere in the template output would be useful to diagnose the problem
Some errors are already caught, therefore not preventing translation from proceeding, but it would still be useful to log them to help diagnose problems:
At the very least, template output may include an "errors" array including all errors caught during its execution (see T302431). The Web2Cit-Server may print this to a new per-template "errors" row or property in the html or json formats, respectively.
Some errors are already caught (...) but it would still be useful to log them to help diagnose problems: