Hi all,
we have got a workflow running with DenyFolder set to BEARB* in the MonitorNode (Folder). AQlthough set, it seems that the files moved to a BEARB*-Folder are still processed. This workflow was running clean on 9.4.x.
I attach the workflow and logs (hopefully the right ones...).
Any ideas?
regards,
tom
[SOLVED] Deny Folders - still an issue? (1.0.0.1)
[SOLVED] Deny Folders - still an issue? (1.0.0.1)
- Attachments
-
- 20200220-1706-1503-6661-b1ce27c0e3b5.7z
- this was not succesful.
- (5.1 KiB) Downloaded 340 times
-
- 20200221-1441-0719-7afa-aac35f8e666e.7z
- this was succesful.
- (5.57 KiB) Downloaded 340 times
-
- Film_xxHash_JSON_LIG_2_NAS002.json
- The Workflow.
- (17.63 KiB) Downloaded 375 times
Last edited by ThomasM on Wed Feb 26, 2020 2:30 pm, edited 1 time in total.
Re: Deny Folders - still an issue? (1.0.0.1)
Hi ThomasM,
Not sure you sent the right logs. All I can find as source was
E:\Capture\Zum_Transcoding\ComOpt\18\16FA9869INV18899.420.avi
E:\Capture\Zum_Transcoding\ComOpt\18\16FA9869INV18899.427.avi
None of these are in a "BEARB*" folder. Also, I'm not able to recreate the issue in the 1.0.0.1 version. But if you send the right logs (if they exist
) I will of course take look at it and if it turns out to still be a problem I have to dig deeper.
-steinar
Not sure you sent the right logs. All I can find as source was
E:\Capture\Zum_Transcoding\ComOpt\18\16FA9869INV18899.420.avi
E:\Capture\Zum_Transcoding\ComOpt\18\16FA9869INV18899.427.avi
None of these are in a "BEARB*" folder. Also, I'm not able to recreate the issue in the 1.0.0.1 version. But if you send the right logs (if they exist
) I will of course take look at it and if it turns out to still be a problem I have to dig deeper.-steinar
Re: Deny Folders - still an issue? (1.0.0.1)
Hey Steinar,
yeah - I still have problems to find the right logs, but comes a time...
But: I solved the problem with the deny-Folders.
What I did:
1. I migrated from 0.9.4.x to 1.0.0.
2. I tried some workflows with small files, size of about 100 MB.
3. Then I let the workflow run in "real life" with big sized Files of about 120 GB ... 150 GB. Then the problem occured.
4. I wrote to this forum.
5. I Tried the update of the proecessors-file from the othe problem with the variables
6. Still problems, Deny-folders were still executed.
7. I re-visited the MonitorFolder-Node. Without doing anything at closing the node with OK I was prompted to save the workflow.
8. I tried other nodes as well - everytime I was prompted to save the workflow.
9. I assume it has something to do with the new features added to the nodes
10. I tried the Workflow with big size files again - running flawlessly!
So, it seems to be a good idea to re-visit every node on importing or migrating to new versions as there could be additions to the features made?
Anyway - I'm lucky right now.
cheers,
tom
yeah - I still have problems to find the right logs, but comes a time...
But: I solved the problem with the deny-Folders.
What I did:
1. I migrated from 0.9.4.x to 1.0.0.
2. I tried some workflows with small files, size of about 100 MB.
3. Then I let the workflow run in "real life" with big sized Files of about 120 GB ... 150 GB. Then the problem occured.
4. I wrote to this forum.
5. I Tried the update of the proecessors-file from the othe problem with the variables
6. Still problems, Deny-folders were still executed.
7. I re-visited the MonitorFolder-Node. Without doing anything at closing the node with OK I was prompted to save the workflow.
8. I tried other nodes as well - everytime I was prompted to save the workflow.
9. I assume it has something to do with the new features added to the nodes
10. I tried the Workflow with big size files again - running flawlessly!
So, it seems to be a good idea to re-visit every node on importing or migrating to new versions as there could be additions to the features made?
Anyway - I'm lucky right now.
cheers,
tom
Re: [SOLVED] Deny Folders - still an issue? (1.0.0.1)
Hello Thomas,
Happy to hear everything is fine now
Yes, the upgrade to 1.0.0 can be obviously a little bit complicated, this new version was rewritten, so some flaws can be meet. But Steinar worked hard to release the last patch(1.0.0.1) and I think most of problems were gone.
Anyway, thanks for your feedback
cheers.
Benjamin
Happy to hear everything is fine now
Yes, the upgrade to 1.0.0 can be obviously a little bit complicated, this new version was rewritten, so some flaws can be meet. But Steinar worked hard to release the last patch(1.0.0.1) and I think most of problems were gone.
Anyway, thanks for your feedback
cheers.
Benjamin