• State Verified Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 2 subscribers
  • Views 11 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

    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:

    1. Split your quarterly export into 30–45 day segments
    2. Export each segment separately
    3. 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?

Reply
  • 0

    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:

    1. Split your quarterly export into 30–45 day segments
    2. Export each segment separately
    3. 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?

Children
No Data