Report export timing out for large date ranges — workaround?

Question

I have confirmed that the Work Order Summary Report is consistently timing out when attempting to export date ranges exceeding 90 days. This behavior is reproducible across multiple browsers (Chrome 124.0.6367.78, Firefox 125.0.3) and occurs for users with both Admin and Manager roles.

Environment Details: 
 
 Account: Enterprise Plan (500+ active technicians) 
 Approximate work order volume: 12,000–15,000 records per month 
 Target date range: January 1, 2025 – March 31, 2025 (Q1 reporting) 
 Error observed: "Request timed out" after ~120 seconds; HTTP 504 returned

Steps to Reproduce: 
 
 Navigate to Reports → Work Order Summary 
 Set Date Range to Custom: 2025-01-01 to 2025-03-31 
 Click Export to CSV 
 Observe timeout after approximately 2 minutes

I have verified that smaller date ranges (30 days) complete successfully in approximately 15 seconds. The issue appears to be related to the volume of data being processed rather than a specific filter or parameter.

From a governance perspective, we require quarterly exports for internal audit compliance. I am seeking either: 
 
 A supported workaround for bulk export (e.g., API-based retrieval with pagination) 
 Confirmation of known limitations and recommended maximum date ranges 
 Timeline for resolution if this is identified as a platform defect

I have reviewed the workaround article for API pagination but would prefer to confirm whether this is the recommended approach before developing a custom solution.

Priya Nair (Staff) · Accepted Answer

Rachel, just to close the loop on this — I've confirmed with our engineering team that the 120-second UI timeout is a current platform limitation for reports exceeding ~8,000 records. Your account consistently exceeds this threshold.

Recommended path forward: 
 
 Use the API method Carlos and Eli outlined above for quarterly exports 
 For monthly operational reports, the UI export should remain viable 
 We're tracking your account for the streaming export beta (targeting Q3)

I've also updated the troubleshooting article to include a direct link to the API pagination guide, since this is coming up more frequently with larger customers.

Let me know if you need help with the audit log integration Gwen mentioned — happy to walk through that endpoint structure as well.

Priya Nair (Staff) · Answer

Hi Rachel, happy to help with this!

You're correct that large date ranges can hit our current export timeout limits. For your volume, I'd recommend a two-pronged approach:

Immediate workaround: 
 
 Split your quarterly export into 30–45 day segments 
 Export each segment separately 
 Combine the CSV files locally (they'll have identical column headers)

Better long-term solution: 
 The API approach you mentioned is actually what we recommend for enterprise accounts with your data volume. Use GET /work_orders with: 
 
 date_from and date_to parameters 
 limit=500 (maximum page size) 
 offset or cursor pagination for reliable retrieval

This bypasses the UI timeout entirely and gives you more control over field selection.

I'm flagging this with our engineering team to review timeout thresholds for enterprise-tier accounts. Would you like me to open a ticket to track this specifically for your organization?

Carlos Vega · Answer

We've been hitting this too. Here's what actually works:

curl -H "Authorization: Bearer $TOKEN" \
 " ">api.fieldpulse.com/.../work_orders

Key gotcha: the total_count in the first response is your loop terminator. Don't trust estimated pages.

Also, add status=completed or whatever filter you need — unfiltered calls will include drafts and cancellations and blow up your pagination.

Rate limit is 100 req/min for enterprise. Should take ~25 requests for your quarter. Sleep 600ms between calls to be safe.