Keli Moffat 12.Aug.03 10:43 AM a Web browser End user issues All Releases All Platforms
Last year, we created a workflow application that runs from the browser. It worked fine during development and tested fine as well. However, now, about once a week, when one of the potential activity owners goes into a document, they run into an Error 500 ("Invalid Document Identifier") when they try to claim and edit it . It happens at the same location on the workflow each time (at an automated activity - send email action type). We have found that updating the process cache manually takes care of the problem, but we don't know why. Is there anyone out there who can shed some light on this issue?