Logging a weird glitch I came across. A workflow failed due to a "missing" encoding profile, although the encoding profile "audio.wav" does indeed exist.
2018-08-23 17:57:28,397 | ERROR | pool-54-thread-1175 | (WorkflowOperationWorker:180) - Workflow operation 'operation:'compose', position:19, state:'FAILED'' failed
org.opencastproject.workflow.api.WorkflowOperationException: Encoding profile 'audio.wav' was not found
at org.opencastproject.workflow.handler.composer.ComposeWorkflowOperationHandler.encode(ComposeWorkflowOperationHandler.java:217)[59:matterhorn-composer-workflowoperation:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.handler.composer.ComposeWorkflowOperationHandler.start(ComposeWorkflowOperationHandler.java:132)[59:matterhorn-composer-workflowoperation:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.impl.WorkflowOperationWorker.start(WorkflowOperationWorker.java:233)[183:matterhorn-workflow-service-impl:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.impl.WorkflowOperationWorker.execute(WorkflowOperationWorker.java:155)[183:matterhorn-workflow-service-impl:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.impl.WorkflowServiceImpl.runWorkflowOperation(WorkflowServiceImpl.java:885)[183:matterhorn-workflow-service-impl:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.impl.WorkflowServiceImpl.process(WorkflowServiceImpl.java:1899)[183:matterhorn-workflow-service-impl:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.impl.WorkflowServiceImpl$JobRunner.call(WorkflowServiceImpl.java:2319)[183:matterhorn-workflow-service-impl:4.0.0.SNAPSHOT]
at org.opencastproject.workflow.impl.WorkflowServiceImpl$JobRunner.call(WorkflowServiceImpl.java:2285)[183:matterhorn-workflow-service-impl:4.0.0.SNAPSHOT]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[:1.8.0_181]
at java.lang.Thread.run(Thread.java:748)[:1.8.0_181]
My systems run upwards of 100 workflows at any given time, almost all of which are using the same workflow definition as the one that failed above. Yet, all others completed without failing with the exception above.