Monitors:Folder deny files by using variables

[michael85]

Hello guys,

Wonderful! I have changed the conditional Node as posted in steinars reply and it works like a charm.
I have also added another condition to prevent files from encoding which were created before today. This also works BUT the folder i want to monitor is heavy filled with approx 3700 files. By starting the workflow, FFAStrans checks every single file in the folder, which tooks a time to read out all the media source properties. Unfortunately I can not move the "old" files to another directory because other subsystems have to access the files in exactly this folder. Is there a way to tell FFAStrans to process only "new" files or do I have to wait until every single file is checked?

There is also another problem. Since the workflow is running and checks file after file i encountered an error on some servers were FFAStrans runs. See screenshot.

Another Question: Since the files always stay in the source directory, do I have to make any setting so that FFASTrans remembers that the files have already been encoded?

[emcodem]

Hey Micahel,

Is there a way to tell FFAStrans to process only "new" files or do I have to wait until every single file is checked?

Thats easy: open the Monitor Folder Processor, click on History in the top menu and hit "Rebuild". All files in the folder will be remembered and not be processed again.

There is also another problem. Since the workflow is running and checks file after file i encountered an error on some servers were FFAStrans runs. See screenshot.

if @admin doesnt reply to that, i'll check in the next days what this means or where it comes from.

Another Question: Since the files always stay in the source directory, do I have to make any setting so that FFASTrans remembers that the files have already been encoded?

Thats the default setting. Do you have feeling that the same files are processed again and again?

[michael85]

Thank you emcodem,
you all helped me very much to bring this workflow to run and i have learned a few things about working with FFAStrans.

The tipp with the history rebuild has lead to success.

The error occurs on 2 of 3 servers. Regardless if a job is running or not.
Maybe it is helpful for the admin to see the mentioned file in the error message. I have attached them.

No, I don't have the feeling that the same files are processed again and again. I just find the setting "Validate records after <n> days" in workflow properties --> Maintenance Tab and was not sure by reading the description of that point. Therefore I thought it was better to ask for it

[admin]

Hi michael85,

The bug you're seeing is due to some information missing that aught to be there. It might be a corrupt workflow but it might also be one of the many issues we have resolved for the upcoming 1.2 release. It's a bit hard to say without having the workflow that initiates the issue. If you know what workflow it is maybe you can send it and I'll take a look and see if it could be some sort of corruption.

-steinar

[michael85]

Hi steinar,

attached you will find my two tiny workflows.
The error comes up really often and I have the feeling that the servers wont encode anymore until this error message is closed by clicking on "ok".
Is there a release date for version 1.2 of FFAStrans?
Maybe it might help if I start from the scratch and rebuild my workflows!?
I'am using FFASTrans 1.1.0.2. at the moment.

[admin]

I'm not able to get your workflow to fail even on the 1.1.0.2 version...But there has been several changes to the code surrounding the issues because I have seen it before so it was addressed. So, for this I think we just need to see how 1.2 behaves. It's scheduled to medio February.

-steinar