Dear users,
We would like to sincerely apologize for the inconvenience caused by the recent update of our service. We deeply regret any issues you may have encountered during the process.
We would like to inform you that we have been working on updating our system. Over the past month, we have actively focused on improving the stability and functionality of our service.
However, during the update, an error occurred, which necessitated a rollback to the previous working version. 😱😢
We apologize for any inconvenience this may have caused.
Some good news: all clients using our service on Clouds have already been updated and are now running on the latest version of our service.
This update was necessary for the continued development and improvement of our service. We are committed to providing you with a more stable and efficient user experience.
We understand that you may have questions regarding the changes that have been made. If you have any inquiries or require assistance, please feel free to reach out to us, and we will be more than happy to assist you.
Once again, we apologize for any inconvenience caused and appreciate your understanding and support. Your trust and satisfaction are our top priorities, and we will continue working towards enhancing our service.
We would like to sincerely apologize for the inconvenience caused by the recent update of our service. We deeply regret any issues you may have encountered during the process.
We would like to inform you that we have been working on updating our system. Over the past month, we have actively focused on improving the stability and functionality of our service.
However, during the update, an error occurred, which necessitated a rollback to the previous working version. 😱😢
We apologize for any inconvenience this may have caused.
Some good news: all clients using our service on Clouds have already been updated and are now running on the latest version of our service.
This update was necessary for the continued development and improvement of our service. We are committed to providing you with a more stable and efficient user experience.
We understand that you may have questions regarding the changes that have been made. If you have any inquiries or require assistance, please feel free to reach out to us, and we will be more than happy to assist you.
Once again, we apologize for any inconvenience caused and appreciate your understanding and support. Your trust and satisfaction are our top priorities, and we will continue working towards enhancing our service.
🍌8❤4👍4🤔2🔥1
How to get new created bot via BB API?
use https://api.bots.business/v1/bots?api_key=API_KEY&count=1
you can put to count any value but with 1 it will be more quickly
All your bots - without count (can be slowly for big bots list)
https://api.bots.business/v1/bots?api_key=API_KEY
It will be working in one hour.
use https://api.bots.business/v1/bots?api_key=API_KEY&count=1
you can put to count any value but with 1 it will be more quickly
All your bots - without count (can be slowly for big bots list)
https://api.bots.business/v1/bots?api_key=API_KEY
It will be working in one hour.
👍8
We've introduced a 250-millisecond read timeout in our database interactions to increase efficiency and overall system performance.
This timeout is essentially a time limit set for our system to get a response from the database. If the set time limit is exceeded without receiving a response, the read attempt is terminated, returning an error. This mechanism enhances our system's responsiveness and capability to handle numerous queries effectively, minimizing potential waiting times.
Further, we're excited to inform you that we're in the process of transitioning to a faster, more efficient database platform. This upgrade will significantly improve our query processing speed, resulting in better performance and reliability. However, this transition will take some time as we're ensuring a smooth and seamless shift to avoid any potential disruptions to our service. We apologize for any temporary inconvenience this might cause and greatly appreciate your patience during this period.
This timeout is essentially a time limit set for our system to get a response from the database. If the set time limit is exceeded without receiving a response, the read attempt is terminated, returning an error. This mechanism enhances our system's responsiveness and capability to handle numerous queries effectively, minimizing potential waiting times.
Further, we're excited to inform you that we're in the process of transitioning to a faster, more efficient database platform. This upgrade will significantly improve our query processing speed, resulting in better performance and reliability. However, this transition will take some time as we're ensuring a smooth and seamless shift to avoid any potential disruptions to our service. We apologize for any temporary inconvenience this might cause and greatly appreciate your patience during this period.
👎7👍2
Dear users,
To optimize our system, we have implemented a 250-millisecond timeout for database read operations. Understanding the possible complexities this could introduce, we would like to provide some recommendations to minimize the risk of timeouts:
Reduce the number of calls to
Limit the size of variable values: When using functions such as
To optimize our system, we have implemented a 250-millisecond timeout for database read operations. Understanding the possible complexities this could introduce, we would like to provide some recommendations to minimize the risk of timeouts:
Reduce the number of calls to
User.getProperty and Bot.getProperty: Try to limit the use of unnecessary variables. The fewer variables requested, the lower the database load, thus reducing the likelihood of a timeout.Limit the size of variable values: When using functions such as
User.setProperty and Bot.setProperty, it's recommended to keep data size minimal. Smaller data volumes process faster, reducing timeout possibilities. Props with data for All bots users - it is not good. Use list here.help.bots.business
Lists | Bots.Business - Help
👎4👍1
Since the beginning of the year, we've seen a substantial 100% increase in traffic. 😱❤️🎉🥳
This growth underscores the necessity of enhancing our system architecture, and we want to assure you that our team is actively working on it.
While we strive to improve our backend, it's also crucial that user-generated code becomes more efficient. An increase in the user base means increased diversity in the code, which can introduce performance bottlenecks, impacting the overall platform speed.
Unfortunately, when user codes are slow, they can impact the platform at large, causing all bots to slow down. As a result, we've had to introduce limits, including the 250-millisecond database read timeout, to maintain BB stability and improve overall performance.
We're continuously looking for ways to balance performance, user experience, and growth, while also maintaining a platform that allows users to build varied and complex bots. We appreciate your understanding and your contributions to improving BB.
This growth underscores the necessity of enhancing our system architecture, and we want to assure you that our team is actively working on it.
While we strive to improve our backend, it's also crucial that user-generated code becomes more efficient. An increase in the user base means increased diversity in the code, which can introduce performance bottlenecks, impacting the overall platform speed.
Unfortunately, when user codes are slow, they can impact the platform at large, causing all bots to slow down. As a result, we've had to introduce limits, including the 250-millisecond database read timeout, to maintain BB stability and improve overall performance.
We're continuously looking for ways to balance performance, user experience, and growth, while also maintaining a platform that allows users to build varied and complex bots. We appreciate your understanding and your contributions to improving BB.
👎65🤬62👍4
Bots.Business
Since the beginning of the year, we've seen a substantial 100% increase in traffic. 😱❤️🎉🥳 This growth underscores the necessity of enhancing our system architecture, and we want to assure you that our team is actively working on it. While we strive to improve…
We have more good apdex now.
Today we try to increase prop reading timeout for +40% from 250 ms to 350 ms
Today we try to increase prop reading timeout for +40% from 250 ms to 350 ms
🤬10👎3👍2🔥1