• State Verified Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 2 subscribers
  • Views 2 views
  • Users 0 members are here
Options
Related

Report export timing out for large date ranges — workaround?

Rachel Nguyen

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:

  1. Navigate to Reports → Work Order Summary
  2. Set Date Range to Custom: 2025-01-01 to 2025-03-31
  3. Click Export to CSV
  4. 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:

  1. A supported workaround for bulk export (e.g., API-based retrieval with pagination)
  2. Confirmation of known limitations and recommended maximum date ranges
  3. 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.

Parents
  • 0

    Thank you both. I have implemented the API approach as described.

    Additional observation: I can confirm that unfiltered requests return approximately 22% more records than expected due to draft and cancelled work orders included in the default result set. The status filter is essential for accurate data reconciliation.

    Current retrieval rate: 500 records per request, ~3.2 seconds per response. Full Q1 export completed in 4 minutes 18 seconds via scripted pagination versus consistent timeout via UI.

    Is there a documented endpoint for retrieving the complete field schema? Some custom fields appear in UI exports but are not immediately visible in the API response payload.

  • 0 in reply to Rachel Nguyen

    yeah the custom fields thing tripped me up too when I first looked at it — they're nested under custom_fields as an array of objects with id, name, and value, not flattened like you'd expect.

    example truncated response:

    {
  "id": "wo_abc123",
  "custom_fields": [
    {"id": "cf_1", "name": "Contract Type", "value": "Annual"},
    {"id": "cf_2", "name": "PO Number", "value": null}
  ]
}

    heads up: if you have a lot of these, the payload gets heavy fast. worth adding include_custom_fields=false if you don't need them and want faster transfers.

    also yeah this timeout issue is a known pain point — there's actually a troubleshooting article on large work order list timeouts that mentions they're looking at streaming exports for a future release. no ETA though.

Reply
  • 0 in reply to Rachel Nguyen

    yeah the custom fields thing tripped me up too when I first looked at it — they're nested under custom_fields as an array of objects with id, name, and value, not flattened like you'd expect.

    example truncated response:

    {
  "id": "wo_abc123",
  "custom_fields": [
    {"id": "cf_1", "name": "Contract Type", "value": "Annual"},
    {"id": "cf_2", "name": "PO Number", "value": null}
  ]
}

    heads up: if you have a lot of these, the payload gets heavy fast. worth adding include_custom_fields=false if you don't need them and want faster transfers.

    also yeah this timeout issue is a known pain point — there's actually a troubleshooting article on large work order list timeouts that mentions they're looking at streaming exports for a future release. no ETA though.

Children
No Data