Stream versus set

A callback is an event. An active snapshot is not another event stream.

Compare anonymized callback rows with a supplied active-notification snapshot. See which identities are callback-only, present in both sets or active-only instead of treating every visible active record as newly posted.

Browser-local worksheet

Reconcile callback and snapshot identity sets

At least one callback and one snapshot row are required. Repeated rows remain counted, while membership is reconciled on the supplied strong identity tuple.

Aliases only · no device access

Ten comma-separated columns: sequence, origin (callback/snapshot), package alias, notification ID, tag alias, user alias, group key, summary flag, optional post time, observed time. Use short aliases—never paste notification text, names, phone numbers or account data.

No diagnosis yet

The worksheet does not connect to Android, Tasker or AutoNotification. It classifies only the identity rows shown above.

How to read the result

CALLBACK_ONLY appears only in the supplied event rows. BOTH appears in the callback and active set. ACTIVE_ONLY was present in the supplied snapshot but not in the callback rows. None of those labels proves why Android or a plug-in emitted a particular callback.