correct. I missed the trailing 0 in my copy-paste

Again my fault (note to self: I shouldn't do debugging when I'm tired).

In fact I've been able to replicate the problem this morning, and I also have the right solution in mind. Please expect an updated by the end of the day (i.e. as soon as I get back to home )

The problem is that in some cases the iso8601 module doesn't return the string date in the a format that Google likes, and your timestamp in particular is one of those that make it spit out bad values. Originally there's already code to manage those cases (it's part of the snippet of code I made you try a few posts ago), but for some reason that I can't come up with, the part of the code that generates the date boundaries for Google doesn't make use of the "workaround code" (albeit being used elsewhere in the code...I gather that the buggy code is probably the very first part of Erminig written, when I did not hit date problems at that moment).

thank you very much for your patience!