This happens with 0.11.4. Note that I can still run backfills but the nominal partition date ends up differing from the actual partition (‘version date’) that feeds through the solids in the pipeline. There is no obvious relation between the partition date and the resulting version date.

I’m not sure what you mean by `but the nominal partition date ends up differing from the actual partition`… is this a separate issue you’re running into?

Queued and in progress lists are empty

As for this: `but the nominal partition date ends up differing from the actual partition`… i am not sure if related or not - I have noticed this after I experienced the error (btw: I find puzzling that I can run backfills when I also see ‘backfill daemon not running’)

As far as I can tell there is nothing pending that can be cancelled in the UI: I take it back, there was a backfill to cancel actually. After cancelling/restarting I don’t have the error anymore

The strange behaviour with differing ‘effective’ and ‘nominal’ partition is also gone now if I run the partition from scratch. If I hit ‘re-execute’ instead, I have the same issue as before. In this latter case ‘Run configuration’ shows the nominal partition in tags but the version date in the config is wrong

You can test this just by going to the

Playground

tab of the pipeline, and selecting the partition in the selector

Actually the problem persists when running a ‘full’ backfill- as opposed to a backfill consisting of a single partition. I suspect this might have to deal with the parallelisation of runs and the use of partials in my code

I am still battling with this. Problem manifests itself when executing a backfill job consisting of several partitions. In this case the ‘version_date’ ends up always being the first partition being executed, whereas the tag reports the nominal partition date. I attach the code below, hopefully you can spot where the problem originates from or suggests way to debug. At this point I am clueless!