Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix 503 server error #352

Merged
merged 1 commit into from
Jan 17, 2024
Merged

Fix 503 server error #352

merged 1 commit into from
Jan 17, 2024

Conversation

vplasencia
Copy link
Member

Related Issue

#349

Does this introduce a breaking change?

  • Yes
  • No

Copy link
Contributor

@0xjei 0xjei left a comment

Choose a reason for hiding this comment

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

Approved! 🆗

In the future, we can use the tx object to handle potential errors in a more granular way. For now, let's continue with your solution. Thank you for your work Vivi 😊

@vplasencia
Copy link
Member Author

Hey @0xjei. We were using tx before but it was not working properly

@vplasencia vplasencia merged commit a47a54a into dev Jan 17, 2024
2 checks passed
@vplasencia vplasencia deleted the fix/503-error branch January 19, 2024 13:51
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.

When working with the Bandada infrastructure (dashboard, api or sdk) you can get the 503 server error
2 participants