Hello,
I’ve taken a look at this, it seems that Cylc 8 is providing the same Jinja2 variables to the workflow as Cylc 7 was so it doesn’t look like an issue with Cylc.
The error is coming from within the Jinja2 logic contained in the workflow itself. We’ve recently added some advice for debugging Jinja2 code into the Cylc documentation which might help.
With debug/log statements you might be able to locate the source of the problem.
The main changes as far as Jinja2 is concerned between Cylc 7 and 8 are:
- Python 2.{6,7} => 3.7+
- Jinja2 v2 => v3
There’s some information on the Jinja2 change in this post - Cylc 8 & Jinja2 v3, it might also be worth having a quick skim of the Jinja2 changelog.
Cheers,
Oliver