Answer
Check the Finance User Groups setup for the users whose orders trigger this background job — a misconfigured or missing Finance User Group assignment has caused exactly this pattern (fails in the background, succeeds on manual re-execution, unaffected by queue changes), since the background execution context resolves finance-related combination rules differently than an interactive re-execution does; correcting the Finance User Group arrangement for the relevant users has resolved this without needing further queue or scheduling changes.