Retrieves an estimated amount of time the backend pipelines are running behind. Journey History events after this time aren’t guaranteed to be available.
The response includes the amount of time (in seconds) processing pipelines are behind.
For example, this API returned 20 minutes. If a contact entered a journey 30 minutes ago and exited 10 minutes ago, only a partial history can be retrieved. Entry events and a few initial activities will be available through Journey History API, while the last activities and exit events won’t.