Trouble identifying "Tombstone exists for queued item; deleting." in ipad logs Playing around with my apple device logs and getting interested in identifying different events.  Many I seem to be able to figure out with a google search and a bit of reading.  However, this one is eluding me.  This is only a small snippet of these events.  The log was compiling at a decent pace, when these particular lines began to appear in a much more rapid manner.  

-The device is not jailbroken, running out of the box ios
-No apps running at time of log
-I do not use Icloud

 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.
 Jan 17 22:40:03 A-iPad suggestd(CoreSuggestionsInternals)[388] &lt;Notice&gt;: Tombstone exists for queued item; deleting.```


This was also referenced immediately after the above 
```MobileSafari(CoreMotion)[326] &lt;Notice&gt;: {"msg":"CLGyroBiasEstimatorClientRemote::unregisterWithGyroBiasEstimatorPrivate", "event":"activity", "client":"0x111b2e550"}```
See: Tombstone (data store). 

In brief, a tombstone is a token in a distributed data storage system that gets put in place when a record is deleted. It's needed for synchronizing different stores on the distributed system. For example, if record 'A' is deleted on one store, when the system tries to sync it may see another copy of record 'A' on a different store, and it won't know that the record was deleted from the first. It might unwittingly sync record 'A' back to the first store, effectively undeleting it. The tombstone tells the system that record 'A' was deleted on the first store, so that the system can sync that deletion to the other stores appropriately.