extend all requests timeouts to 3 minutes #242
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Description
This PR extends the global HTTP timeout for all Base44 API requests from the default (10 seconds) to 3 minutes (180,000ms). This change addresses timeout issues encountered with long-running API operations such as project deployments, entity pushes, and other resource-intensive tasks that may take longer than the default timeout to complete.
Related Issue
None
Type of Change
Changes Made
timeout: 180_000configuration to thebase44Clientky instance insrc/core/clients/base44-client.tsbase44ClientandgetAppClient()Testing
npm test)Checklist
Additional Notes
This timeout value (180,000ms = 3 minutes) was chosen to accommodate long-running operations while still providing a reasonable upper bound. The change is non-breaking as it only extends the timeout window rather than reducing it. Operations that previously succeeded will continue to succeed, and operations that previously timed out may now complete successfully.
🤖 Generated by Claude | 2026-02-12 16:45 UTC