I have encountered something that has basically left me scratching my head (BP 6.4):
Description: I have a file with about 5000 cases. First thing the process does is to add these cases in the queue. But before it adds these cases to the queue, it cross references the case with a database to check if any of them are already closed. If their are cases in the file that are already closed (in my file there are 321 cases that are already closed), process does the following: it first adds all cases that are NOT closed in the queue and then adds all cases that are closed in the queue. Process then marks all cases that are already closed as exception in the queue
Issue: I'm seeing bizarre behaviour at this stage: what happens is that when the process marks the closed cases (321 cases from my file) in the queue as exception, not all of them get marked as exception. I always get about 40 odd cases that don't get marked as exception. But if i check a few hours later, they are marked as exception. As I am stopping the process after cases are added and marked in the queue, none of these cases have been worked.. they just seem to take time before they get marked as exception
Has anyone seen this behaviour?
As answered in the comments:
once the 40 odd cases are marked as exception, date\time of exception is set to exactly the time when the initial cases were marked as exception (well i say exactly.. round about the same time) and not 2-3 hours later when these cases were marked as exception
Knowing this fact, it is likely that what you're observing is something purely cosmetic. Unless in your workflow you require this data to be up-to-date in real time, it is unlikely that this affects workflows' functionality in any material way.