This is indeed strange, as your custom action is scheduled correctly.
Also, the naming is not important here because you call the file using a formatted reference (with the [# prefix)
If possible, could you please create a sample project that reproduces this problem and forward that to me (+ the temp file) so I can run some more tests on my end?
I have tried to reproduce this but it worked correctly on my end.