You are viewing limited content. For full access, please sign in.

Question

Question

Workflow Warning Message - "Retrieve PDF Form Content" Activity is Reporting "The directory is not empty"

asked on March 6 Show version history

This is not an urgent thing, but I'm seeing a warning I haven't seen before and it isn't really clear what is going on.  I'm wondering if anyone has any suggestions.

I have a workflow that has been running for years (more than a decade) with minimal modifications, and it runs dozens of times or more every day.

In the last week I've started to see a warning message from this workflow that I've never seen before.

The workflow is triggered by the creation of an entry in the repository within a specific folder.  The entries are all created using Import Agent which in turn is triggered by staff members placing specific files into a network folder.

Import Agent Version: 12.0.2510.614

Workflow Version: 12.0.2511.266

The updates to both programs were completed several few months ago, so this probably isn't a result of anything introduced in the upgrade.

As mentioned, this workflow has been running on demand dozens of times a day for over a decade - I've never seen it do this message until now.  But I've seen it once or twice a day for about a week now.

The first activity on the workflow is a "Retrieve PDF Form Content" activity and in these cases it is reporting "The directory is not empty".

The majority of the instances of the workflow are not reporting the message, just a small handful of them (once or twice a day for about a week now).  2% of the instances over the last 2 weeks, with no obvious pattern to the ones that had the message.

As best I can tell, the activity is operating as expected, because it's required for everything that follows, and both this workflow and another that it kicks-off at the end, are both completing fully and accurately.

So this isn't stopping anything, it isn't a problem, just a curiosity.

Has anyone seen this before or have a suggestion where I could look to try to glean more information about it?

Thank you!

0 0

Replies

replied on March 6

Is it recorded as a warning or an error? Could you look for the full error message in the activity error logs (either on disk in <install directory>\Logs\Errors or from the Workflow Admin Console\Monitoring\Error Logs\Current error logs) and post the full error here?

Most likely, the temp Windows folder for the user specified in the Workflow Server's service login is full. 

0 0
replied on March 6

It's a warning, not an error.  I checked all of those error logs (in both places just to be certain) and cannot find anything near the timestamps of the recent items I'm seeing.  Couldn't find anything searching for keywords like "folder" either.

0 0
replied on March 6

I did notice this as I was re-reviewing the workflow history - I see the same message regardless of whether I'm looking at a workflow instance with the warning or an instance without the warning.

Because of that, I decided it wouldn't hurt to re-import the master file again, so I did that on the Admin Console > External Objects > Attachments
It now shows version 13 instead of 12.

I'm guessing that won't make any difference to anything - because that message about the error loading PDF went away on all of the historical runs of the workflow, even ones from before I made that change - and it went away on both the ones with the empty directory warning and the ones without the warning - so I don't think this actually had anything to do with the warning...

0 0
replied on March 6

Ultimately, this isn't a problem really since the workflows are still working properly, just a curiosity.

0 0
replied on March 9

Oh, the master PDF is missing from the Workflow volume. Was this server moved without moving its volume?

As for the message, it would only impact design, not the runtime. That file is used to pick the fields in the PDF. Once the workflow is published, the runtime will just use the field definitions, not the PDF itself. 

0 0
replied on March 9

The last changes we made on that server (other than upgrades) was 4 or 5 years ago - so maybe it's been like that ever since.  You are right that it doesn't appear to have impacted the runs of the workflow at any time.

So that was just a side quest and didn't have anything to do with the messages that I started this post about.

0 0
replied on March 10

Just confirming that change didn't resolve the "The directory is not empty" warning - I had two more of them yesterday.  Hadn't expected it to, but just confirming.

Still not showing on error logs or triggering a try-catch activity - and still not causing the workflow to fail or anything.  Just a weird warning.

I check daily for all workflows with errors or warnings, which is the only reason I'm even noticing these.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.