File Reading Timeout for Large Files in Deployed Edge Worker

Bug Report:

Summary:
When attempting to read files that require more than 2 minutes to process, the deployed edge worker times out, resulting in incomplete or failed requests.

Steps to Reproduce:

• Deploy an edge worker that reads a large file (size sufficient to require >2 minutes to process).

• Initiate the file reading operation.

• Observe the request timing out before completion.

Observed Behavior:
Requests for large files (exceeding size or processing time limits) consistently time out after approximately 2 minutes, failing to deliver results.

Expected Behavior:
Large files should be processed successfully, or clear feedback provided about system limitations.

Transparency on Limitations:

• Maximum file body size: 128 KB when using json() or text() methods for response buffering in EdgeWorkers[3].

• Timeouts: Current processing time cap is ~2 minutes for a single request.

• Token limits: Not documented in the provided sources, but large file size or token count may contribute to timeouts or truncation.

• Additional: Lamatic’s Extract from File node provides file size and metadata, but does not specify processing time caps[5].

Requested Improvements:

1. Document and Surface Limitations:

   • Clearly state maximum supported file size, processing time, and any token or content size restrictions in user-facing documentation and error messages.

2. Improve Timeout Handling:

   • Implement user-friendly error messaging when a timeout occurs, specifying the cause (e.g., exceeded time or file size limit).

   • Consider chunked or paginated processing for large files to avoid triggering timeouts.

3. Increase Timeout Thresholds:

   • Where feasible, raise timeout limits for file reading operations within edge worker constraints, or provide configurable timeout settings.

Impact:
Limits the usability of edge workers for processing large files and leads to unclear errors for users unaware of these constraints.

References:

• EdgeWorkers body size and processing limitations[3]

• Lamatic Extract from File node troubleshooting and file metadata[5]