For example, if I edit the firstName of a candidate and save, then soon (within 1 minute) edit the lastName of a candidate and save, ONLY the history of the lastName edit is returned as part of the subscription. The history of the firstName is NOT included in the subscription.
I use automation to update some field every 15 minutes and those are tracked by a subscription, but my experiment with quick updates was not completely tracked.
Beware if you're using the subscriptions to trigger anything on a field update. There's a chance you might miss something.
This is Dan again with Bullhorn Support.
This is correct. The subscription generally used to track that there WAS an update to the record, not necessarily everything that has been changed. In most implementations, the existence of an event on a record will trigger the integration to just grab the entire record.