Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
jmd
Contributor
Contributor

tWaitForFile : always wait 1 minute

Hi,
I set the time between iterations to 1 (second)
and I tried "when a file is created" or "when a file is updated" as the trigger
But the component (in command line execution) always wait 1 minute, even if the file is there before 1 minute
What's wrong ?
I'm in version 5.2.0
Labels (2)
13 Replies
jmd
Contributor
Contributor
Author

Sorry, it's 2 minutes (120 seconds), not 1
120 iterations and 1 second between iterations
But 1 or 2 minutes, this is the same problem : it works in studio and not in command line
Anonymous
Not applicable

Hi,
it's 2 minutes (120 seconds), not 1
120 iterations and 1 second between iterations

Do you mean one of your iteration last for 120 seconds? How did you calculate it? I mean use what? a counter? Or you found there are 120 iterations in your job run time for 120 seconds? If so, that means time between iteration is "1" second, it isn't right?
Best regards
Sabrina
jmd
Contributor
Contributor
Author

Did you have look at my screen captures ?
It shows precisely the configuration of the component :
1 second between iterations
max iterations : 120
You don't need a counter !
And concretely, when it executes, it waits the max time before exiting the component, while a file is present since many seconds
jmd
Contributor
Contributor
Author

So, nobody has an idea ?
Nobody has encountered such a problem ?
The files to wait for are on a network drive, with a UNC path ( \\edi_server\path_to_folder\ )