If the original item is not totally and completely gone you can run into a condition where the pc is on a persistent F/N with regard to it but it’s still there slightly and nothing reads but it only F/Ns.

If the original item is not totally and completely gone you can run into a condition where the pc is on a persistent F/N with regard to it but it’s still there slightly and nothing reads but it only F/Ns.

What you can do in that case is:

What you can do in that case is:

1. take the pc off auditing for a few days while the persistent F/N dies out and the environment keys something in and continue then with the assessment of that original item or

1. take the pc off auditing for a few days while the persistent F/N dies out and the environment keys something in and continue then with the assessment of that original item or

2. go on with some other original item that does read and make a big clear notation in the pc’s program to come back to the original item after you have run some other original items on the case.

2. go on with some other original item that does read and make a big clear notation in the pc’s program to come back to the original item after you have run some other original items on the case.

If you get stopped by a persistent F/N and some condition is still there, don’t use an F/N as an excuse not to come back to the original item!

If you get stopped by a persistent F/N and some condition is still there, don’t use an F/N as an excuse not to come back to the original item!