When reading your write-up I kept thinking about failed tasks I have seen in the past. They were caused by network issues or the task computer being offline or something external. But then I realized you said they never even made it to the task list. That means it had to be something internal to the workflow that didn't work.
That makes me think I would need to walk through the vault/workflows and:
- Make sure all the users have permission to activate the tasks.
- Make sure the tasks are set to correctly work for the appropriate file type -- don't create a dxf file for a sldprt file.
- Were the files in the correct states?
- Is it positive that it only happened this one time?
If the transition happened but the task was not sent to the task list there must have been some condition of the transition that did not meet the requirements of the files went around the wrong way.
I have had a huge number of tasks not complete, but if the transition worked correctly they were always in the list.
Thanks for the reply. Yeah, the weird thing is I came to the same conclusion that it had to be something internal.... except not with the workflow since it has been this way for quite some time and as you will see below, not really an option. So here are some images to help paint the picture.
All files went through here on this day starting from Development Pending Approval through on to Development Released:
I am actually the one that did the "Approve" transition on all of these and the two automatic transitions just verify that my name got put on the data card really. The only way to be in the "Development Released" state is to go through the "All Approved" transition. And here is all the info on that:
All our tasks are specifically run by our "epdmtask" user on a dedicated server.
So the transition DID happen as you can see and everything is in order for it (it hasn't changed and works fine).
I was able to find some example "Report Generator" files in the KB that allowed me to export the Revision Variable for all the files I wanted to from our vault. I ran a couple different times and put into Excel and manually went through every pdf we have in our released folder (that is where they all go) and double back and forth checked ALL drawings revisions matched the pdf sitting in the folder. If not it was because the file is already being revised again and so I marked it as such, or the task never ran (the issue I'm talking here about). So all said and done out of over 1300 pdfs the files from this specific day are the ONLY ones that didn't match revision that should be there.
So, I manually re-ran the tasks to bring them all up to date. (pdf/dxf/step) and now I don't know what else to look at for a root cause! I even had our IT Department look through their logs for that day and they said there was nothing that happened that should have caused an issue with any of our PDM Vaults.
So I'll keep looking, but don't know where next.
That makes me wonder if when a transition is initiated if all the actions are done from the workstation or if the archive server does them. If the tasks are launched from the workstation maybe there was something in the water that day that didn't allow the workstation to submit the task.
To bad you are not able to reproduce the issue. That would make it easier to figure out.