FFAStrans forum

Hi KalenXII, welcome to the forum and thank you for using FFAStrans!

Is this only happening on one particular workflow or all of them? Also, is the file picked up if stopping and starting the workflow?

-steinar

Hello,

Picking up files has become much better than in previous releases. Current version 0.7.7 is pretty good concerning that.
Occasionally files were not picked up here too (the files are moved or copied over to the watchfolder).
For about 3 weeks we stop and start every workflow in the morning (without clearing cache, that would be deadly for us). Since doing that picking up files is more reliable. The situation is still not perfect but as near as it can. We are not confronted anymore with workflows which are running 2 weeks fine and then stop picking up files.

Best

Taner

admin wrote:Hi KalenXII, welcome to the forum and thank you for using FFAStrans!

Is this only happening on one particular workflow or all of them? Also, is the file picked up if stopping and starting the workflow?

-steinar

So far it's just this one workflow. But this workflow has many more files coming through it than the others, usually 100+ per day. Stopping and starting the workflow doesn't help and neither does clearing the workflow history though I have this workflow set to remove the original from the history cache anyway as I use a command executer to delete the original file at the end of the workflow. Only way I've found to get the workflow working again is to create a new one then copy and paste all the processor blocks into the new workflow but then after two weeks or so the new workflow will also stop processing new files.

When you have a "broken" workflow I would like for you to zip the content of the "FFAStrans\Processors\.cache\wfs\<workflow-id>"-folder and send it to me. It might give me some clue on what's going on.

-steinar

admin wrote:When you have a "broken" workflow I would like for you to zip the content of the "FFAStrans\Processors\.cache\wfs\<workflow-id>"-folder and send it to me. It might give me some clue on what's going on.

-steinar

Here's the workflow that's currently not working. If I add a new file to the folder it will create a .txt file referencing it in the Processors\.cache\wfs\20160929172310\mons\20161129-131247-461-1F205F02F1C0\i folder but will never start processing it.

Steinar, the script is manually executed, no doubts.
And it temporary resolves the problem, till the next time, not prevents it forever.

Has anybody found any more information about this issue? We're still having it in the latest version and so had to stop using ffastrans until it's resolved.

I'm sorry to read that, KalenXII. Can you and Alexander(kibi) please check the "FFAStrans\Processors\.cache\tickets" folder and see if there are some old files stuck there?

-steinar

Good news. In our testing this issue appears to have been fixed for us in the 0.8.0 release.

Great!