It may indicate that it was unable to find the source of the call due to other portions of Responder locking the Feeder.
It may resolve itself once the locks are removed. Another option is to manually create a fault and then cancel the incident. The call will then be re-assigned to the proper upstream incident.
Thanks for your answers. Is there another way to fix this, making changes in the data base?
Thanks in Advanced.
We are seeing this behavior in our test environment, where there is conceivably no contending activity in Responder.
Can you provide more details on what "other portions of Responder" might be locking the Feeder?
Also, we need clarity on the 2nd option. In this scenario, the incident was not created until 1 hr 48 min. later.