The Discover Scanner Doesn't Push New Sigs

Nobody is around but me.  Earlier today, I ganked a Heron downstream from my EOL wormhole.  Now, our static wormhole has timed out and poofed.  I check: three sigs in my home system, as expected.  We have a Sizeable Perimeter Reservoir (a gas site) that I've been eyeing for a while.  Carebears gotta care.  Since we are now zipped up via the hands of Father Time, it's a good time to suck some gas.  In fact I have been planning this since I came back out of the old C4a: I already have my second-account alt logged on and ready in a Venture.

I warp over to see if the gas site has been instantiated yet today.  Yes, there are sleeper frigates.  Great.  I warp back to my POS and refit into a Drake.  Precision heavy missiles will do the job efficiently, off a cheap platform.  I warp to the gas site and engage.  It takes three hits to kill each frigate, and the job is soon done.  As I kill the last frigate, I warp in my alt to the C50 cloud and start sucking gas. When the sleeper dies, I warp back to my POS to get a salvager.

Now I warp out and salvage.  It's a lucky day for me: four nanoribbons from the six frigates.  (Often you get none.)  Now I warp back home and dump off my salvage.  My plan is to log out and log on my "peasant", a same-account alt character with just production skills relevant to wspace life.  (Those being: PI, sucking gas, and mining rocks, and also scanning in case of emergency.)  Von can only use T1 gas miners, whereas my alt can use T2, which means a 50% higher gas sucking rate.  It's worth the minute or two logging in and out.

I log in the alt and warp to the C84 cloud, and start sucking gas.  Then I get my two alts into a fleet so I can fleet-warp off if needed.  And then, I notice the discovery scanner.

There are four sigs on my "peasant's" discovery scanner.  I look over at the other screen.  There are still three sigs on my alt's scanner.  Interesting.  It's probably a wormhole; most new sigs are.  I check dscan, and there are no probes or ships other than mine.  We are in a gas site, which must be probed down.  I am in Ventures, which are tiny and moving and have warp core strength built in.  So, I feel reasonably safe.  I keep gas mining, at least for now.  First priority is to check and see if the new sig is a wormhole.

I fire probes and study the system map.  Yes, there is a new sig in the outer system.  I put my probes there and start scanning.  A few cycles later, and I have it: it is a wormhole, and it is a fat one.  K162 by the signal.

Now I check my second-account alt, and it still does not have the new sig yet.  Since I have noticed a character not seeing a new sig before, I figure this is a great time to perform an experiment.  I am not going anywhere, and I can dscan just fine on my main screen.  I will not do anything on my second account, and just wait for the new sig to be pushed to me.  How long will it be?

Meanwhile, I am sucking gas and hitting dscan like a fool.  Nothing.  Minutes pass.  The C50 cloud is sucked, and I microwarp over to the C84 cloud.  Dscan, dscan, dscan.  More minutes pass.  Finally, the site is exhausted, and I warp both characters back to my POS.

The second account was never updated that I noticed, and I was watching.  It had three sigs the whole time.  When I get back to the POS, I notice three sigs still.  When I compare, I find that both accounts now see the same three sigs.  My guess is that when the gas site despawned, it triggered the discovery scanner to update.  But the new sig, whenever it came, did not.

Looking back on it, I think it likely that the new sig was there when I was killing the sleepers in the Drake.  (Shudder.)  It had not been pushed to me when I was sitting there AFK before, and I probably did not check my discovery scanner when I changed ships.

My current theory on how the discovery scanner works is that new site spawns (which includes K162s in particular) do not trigger its autoupdate.  Old sites despawning do trigger an autoupdate.  This means that hunting through wormholes you instantiate should still work, assuming the potential victims do not know to force-update their discovery scanner.

If you have information confirming or falsifying my theory, please do make a comment.  Further research, as they say, is indicated.

Update: several commenters say I am wrong.  I know it is buggy sometimes, because I explore and see the lack of update in new systems.  So, maybe what I observed is a bug.  Still, even if that is so, it gives one the hope that hunting in wspace through non-K162s can be successful.