Scheduling problem with "second-order pointers"

[JorMaister]

I was scheduling a small project that failed at some point. The error indicates that the tomograms (precedents) are None, while they are not. The key point is that it's a "second-order pointer" which means that the input involved is a set of subtomograms that points to a set of coordinates (well-detected by the scheduling procedure) that points to a set of tomograms (the precedents, the ones that are not detected). See the figures below for more details:

The scheduled project:

The run.stderr log:

The schedule.log: