0
Answered

API Timeout Issues After Upgrade to XTRF 7?

Cori Alcorn 2 years ago in API updated by Łukasz Kaleta (Senior Customer Success Manager) 2 years ago 7

Is anyone else having issues with API Timeouts after upgrade to XTRF 7? Several of our main integrations are now failing since our upgrade, and they are all /browser/csv calls that are trying to generate CSVs. When I look in the logs, it looks like an error is being thrown saying the max temporary file size has been exceeded. These are the same exact scripts that were running on XTRF 6 before the upgrade.


I have a ticket into XTRF, but just curious if anyone else has a) run into this since upgrading, b) got it resolved through XTRF support and c) if anyone has found a way to skip the CSV download and instead loop through the pages of the browser call and compile all of the rows into a json/CSV format directly?

Answer

Answer

Hi Cory, we use the API extensively. Since upgrading to XTRF 7, I didn't experience any of the said timeouts. We have been generating reports/csv reports with all our data, approx. 1500 entries. Though, it did seem to be not fully idem potent and the results varied on every refresh.

We came up with an other solution:

1. Send a CSV file every hour to my e-mail address with the Periodic Jobs (XTRF --> Settings --> Integrations --> Periodic Jobs). You can select any View you'd like.

2. Have an e-mail reader automatically read the e-mail and save the CSV into your database

3. Run a report on the CSV within your database

+1

We do the same thing as you, but we haven't had any issues. We also generate CSVs. But our largest export currently has 47 fields and about 3,000 records. We haven't had any issues with that timing out. Maybe as our database grows we'll need to keep an eye out for this? 

Yeah this report has 3200+ entries and 15 columns. So more records, but many fewer fields.  So not sure what is going on. I got a feeling that the temporary file size limit was altered during upgrade (this happened to our max upload size limit one time too).  But they are still out on holiday so not response yet.  Will update here.


Anyone have any luck just looping through the JSON results of the /browse call and then parsing that instead?

This is pretty cool looking, I have to admit I am not very savvy in what I do know, and I don't know .NET, so I may have to spend some time learning before I can make this do what I think it looks like it does. Cheers Robrecht!

Answer

Hi Cory, we use the API extensively. Since upgrading to XTRF 7, I didn't experience any of the said timeouts. We have been generating reports/csv reports with all our data, approx. 1500 entries. Though, it did seem to be not fully idem potent and the results varied on every refresh.

We came up with an other solution:

1. Send a CSV file every hour to my e-mail address with the Periodic Jobs (XTRF --> Settings --> Integrations --> Periodic Jobs). You can select any View you'd like.

2. Have an e-mail reader automatically read the e-mail and save the CSV into your database

3. Run a report on the CSV within your database

Thanks Dennis. Yeah this seems to be an issue in our system. The postgre database settings must have changed because we have been exporting the same and larger views for the last year and the timeout just start d happening on the upgrade. Unfortunately I don’t see a way to shrink our needed reports. So I will see if it can be fixed by support.