The nightmare of long copy jobs: Solutions for the failures?

[admin]

So, did the tweak help?

[Mesh]

Later this week, I should have another big copy job. That will give me a chance to test it out. I'll let you know how it goes!

[Mesh]

Just to test the basic functionality, I set that key to 1000 ms, but it doesn't seem to be working. The copy jobs are starting as soon as the prior jobs are done - no delay is occurring.

[admin]

Just to test the basic functionality, I set that key to 1000 ms, but it doesn't seem to be working. The copy jobs are starting as soon as the prior jobs are done - no delay is occurring.

Try 5000 ms. Just to make sure.

[Mesh]

I just tried 5000 ms as well as 10000 ms, no go. It just hops right from one to the next.

However, I think XY decided to be dyslexic about your instructions - when I tested those higher values, I noticed that after the final copy job finished, it was several seconds before XY responded to my attempts to interface with it. I tested this multiple times. Once I reverted the key back to zero, that post-last-job delay went away and XY was once again instantly responsive after a set of copy jobs finished.

[admin]

I'll check that tomorrow...

[admin]

I'll check that tomorrow...

OK, there was a little bug in that the delay was also applied after the last job. This will be fixed in next version.

But the basic functionality works. Ensure that both Configuration | File Operations | Enable background processing and Configuration | File Operations | Queue file operations are checked.

[Mesh]

OK, there was a little bug in that the delay was also applied after the last job. This will be fixed in next version.

But the basic functionality works. Ensure that both Configuration | File Operations | Enable background processing and Configuration | File Operations | Queue file operations are checked.

They were both checked, and the basic functionality absolutely did not work - at least on my end. There's no mistaking a 10 second delay with immediately coming up, but I'll try it with the next version and let you know how it goes.

[admin]

OK, there was a little bug in that the delay was also applied after the last job. This will be fixed in next version.

But the basic functionality works. Ensure that both Configuration | File Operations | Enable background processing and Configuration | File Operations | Queue file operations are checked.

They were both checked, and the basic functionality absolutely did not work - at least on my end. There's no mistaking a 10 second delay with immediately coming up, but I'll try it with the next version and let you know how it goes.

It now should be: job1 - delay - job2 - delay - joblast

[Mesh]

It now should be: job1 - delay - job2 - delay - joblast

Of course I read that as ending in "job blast", and found myself wondering why you didn't like me.

Just to clarify the timeline, this bug will be fixed in the the *next* beta? Or the one you just posted? You're so quick on fixing bugs, it's hard to tell exactly when it happens sometimes.

[admin]

It now should be: job1 - delay - job2 - delay - joblast

Of course I read that as ending in "job blast", and found myself wondering why you didn't like me.

Just to clarify the timeline, this bug will be fixed in the the *next* beta? Or the one you just posted? You're so quick on fixing bugs, it's hard to tell exactly when it happens sometimes.

Should work in v9.50.0102. At least it does here.

[Mesh]

I just tested v9.50.0102. The delay feature now works properly in both regards. Thanks, Don!

[admin]

I just tested v9.50.0102. The delay feature now works properly in both regards. Thanks, Don!

Good. Let me know if it actually helps solving your original problem.

[Mesh]

Will do!