For cases that are limited to entities/journeys in the Production environment, the Customer Support team may require reporters to gather relevant API responses.
One such example is the Journey Audit Logs, or Journey Events API response.
We can use this API response to analyse the exact history of each stage/task/process
Go to the Journey in question
Open Browser Dev Tools by pressing Shift+Ctrl+i (Windows) or Command+Option+i (MacOS)
Go to the Network tab of the Browser Dev Tools window and ensure the Preseve log checkbox is checked:
On the affected journey, click the Audit button:
If there are multiple pages of Audit records, please set Rows per page to ‘All’
! IMPORTANT NOTE:
It is crucial to select Rows per page 'All' if there are multiple pages, otherwise the API response will not contain the full audit details and we will require a new captureIn the Browser Dev Tools window, click on the latest journeyEvents ‘fetch’ call:
NOTE:
there maybe multiple of this API call in the network logs.
If so, please select the ‘fetch’ call closest to the bottom of the list.Go to the Response tab and copy-paste all the contents onto a notepad .txt file and attach this file to your ticket in Intercom.