Chris,

I'm testing the folder export tool from Qfiche for a customer. The workflow I built works great If I manually run the workflow. However, even after setting up normal starting rules It doesn't seem to want to run automated.  I've replaced the tool and used the typical 'route to folder' tool and the automation worked fine. So I have it ruled down to some sort of set up error that I am doing wrong. 

Any help is greatly appreciated!

I wonder if it's a permissions issue? I notice it's going into your user space. The user that workflow runs under needs access to this folder. If workflow is running as System it probably doesn't have access to it. 

You might try pointing it at a non user space on your C drive to see if it works. (Maybe something like c:\TestOutput). I'm assuming you've already given it enable file browser permissions as per the instructions otherwise I don't think it would execute when you tested it. 

However when you test it you are actually executing the workflow under your permissions. This sort of issue pops up all the time when testing scripts as well. So if you point it to something outside of the user space it might work under the default SYSTEM login. (and even if you have another user workflow runs under, it probably doesn't have access to YOUR userspace!)

Otherwise, I'd send an email to cliff. Since it's his product he might be able to help better than I would!

-Chris

Corey - The activity will report any errors or warnings back to workflow and it also returns 'Success' and 'Return Message' tokens.  Did anything show up in the workflow Messages tab when the workflow gets triggered with the starting rule?

Hey Guys,

Thank you for the responses! and Cliff, thanks for the email, I saw that as well. I did make the starting rules on a schedule but am still having the same issue.  All permissions are set up per the instructions. However, I have not tried moving the folder off of the user space. Let me try that, and I will let you know how it goes.

Unfortunately this did not solve my issue. Again, it worked when I force it to run. But it will not run automatically. I have also refreshed/restarted my services just to be safe.

Here is what my workflow looks like when I run it manually.

The last screenshot indicates the workflows terminated, but the previous ones are from a running instance. Can you open a terminated instance (or if you're starting a new one, press F5 after you open its details to refresh the data)? Then take a screenshot of the Messages tab showing the termination error.

I F5'd my most recent test. Screenshots attached.

I also just found this tab. I thought I selected a path but I notice it looks blank.

Can you post one that you tried to run through workflow that errored out? so we can see any error messages under the messages tab?

On that 9th screenshot you posted with all of your previous runs, dbl click on one of the terminated ones (with the red x) and post what it shows in the messages tab.

sure thing. This error only seems to be because it was a zero byte file.  I've run this with normal docs too. Same result. I have tested this on two separate computers.