Skip to content

Conversation

@SandipBajracharya
Copy link
Collaborator

@SandipBajracharya SandipBajracharya commented Feb 3, 2026

Changes

  • trigger retry when hitting dropbox rate limit or server error
  • logic to handle dropbox rate limit case and retry after specified time in response header

Testing Criteria

Loom

- [x] trigger retry when hitting dropbox rate limit or server error
- [x] logic to handle dropbox rate limit case and retry after specified time in response header
@linear
Copy link

linear bot commented Feb 3, 2026

@vercel
Copy link

vercel bot commented Feb 3, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dropbox-integration Ready Ready Preview, Comment Feb 3, 2026 0:29am

Request Review

Comment on lines -73 to -81
if (!response.ok) {
const retryAfter = response.headers.get('Retry-After')
const error = new Error(`Request failed with status ${response.status}`) as StatusableError
error.status = response.status
error.retryAfter = retryAfter ? parseInt(retryAfter, 10) : undefined
throw error
}

return response
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Arent we going to throw DropboxResponseError from manual fetch from the DropboxAPI?

Copy link
Collaborator Author

@SandipBajracharya SandipBajracharya Feb 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason I removed this is because we can customize the error message from the function level that uses this manualFetch and we don't have to use try catch again.

@SandipBajracharya SandipBajracharya merged commit e5e0ec6 into main Feb 3, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants