We’ve recently released a feature allowing SaaS Admins to export the full history of a run to a file format. The file format was chosen because for very large runs, the job history can easily add up to around 100MB.
You can use this SaaS API call to receive a link to the debug and output history:
GET https://api.blendr.io/v1/accounts/{accountguid}/blends/{blendguid}/runs/{jobguid}/export
The Account Guid, Blend Guid and Job Guid can be retrieved via other SaaS API endpoints.
In this Postman example, you can see that the API response includes both a 'debug' and 'output' link. The former returns the full debug history, while the latter only includes the history of the output blocks.
![LauraLangenaken_0-1623425596477.jpeg LauraLangenaken_0-1623425596477.jpeg](https://community.qlik.com/t5/image/serverpage/image-id/56695iE9C8DDC09C8393F8/image-size/medium?v=v2&px=400)
The debug or output files can then be opened in a browser. It is available via that link for around 20 mins before the link expires.
The raw data available in this file looks like this and can be exported to other systems for logging.
![LauraLangenaken_0-1623682509681.png LauraLangenaken_0-1623682509681.png](https://community.qlik.com/t5/image/serverpage/image-id/56785iB854710E3C2F94CF/image-size/medium?v=v2&px=400)
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.