Hi Darian, do you have any additional logging about the substitution error in server.log? If not, you can try enabling this to see if you get the actual error:
<appender name="acceleration" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${dremio.log.path}/acceleration.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${dremio.log.path}/archive/acceleration.%d{yyyy-MM-dd}.log.gz</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
<encoder>
<pattern>%date{ISO8601} [%thread] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>
<logger name="com.dremio.exec.planner.acceleration" additivity="false">
<level value="debug" />
<appender-ref ref="acceleration" />
</logger>
<logger name="com.dremio.reflection.bup" additivity="false">
<level value="debug" />
<appender-ref ref="acceleration" />
</logger>
<logger name="com.dremio.reflection.ReflectionTracer" additivity="false">
<level value="debug" />
<appender-ref ref="acceleration" />
</logger>
The log message will contain the job id in the thread name to help you find the relevant messages.