Named subroutines containing probe ops cause backplot errors

I believe that I have figured out my problem, however I don't quite know how to fix it. I'm using subroutines to perform different types of feature probing operations. An example program would look something like this:

preamble
o<probe_z> call [...]
o<probe_xy_boss> call []
end

When I load one of these gcode programs, I immediately get "unknown word starting with c" errors from the 3D plotter. It seems like the plotter isn't recognizing the syntax for named subroutines. If you ignore the error, then the first subroutine will run without issue. After the first probe is completed, the error will appear again for the second o code and terminate the program. I attempted to fix this by wrapping each call in a conditional like this:

o100 if [#<_task> EQ 1]
o<probe_z> call [...]
o100 endif
o101 if [#<_task> EQ 1]
o<probe_xy_boss> call []
o101 endif
end

This stopped any errors from appearing prior to cycle start. The first subroutine will execute without issue, and then the error will get triggered again immediately after the first probe. Limiting the file to a single subroutine solves the issue. The #<_task> wrapping method doesn't seem to work more than once in a file in this situation. I suspect that this has something to do with the fact that the first subroutine contains a probe operation which limits the lookahead of the controller's planner. Perhaps the backplotter is getting re-triggered after the first probe operation, but the machine is still in automatic mode since it's mid-file? Any ideas would be appreciated. I'm using probe-basic.