https://discord.gg/botpress logo
Table Rows quota remains at 990/1000 after deletin...
# 🤝help
e
Hi, I'm using a Pay-as-you-go workspace and my Table Rows usage remains at 990/1000 (99%), although all table rows have been deleted. I verified the actual tables using the Botpress Tables API. GET /v1/tables returns only these three tables: - RouterAgentTable — factor 1 - Int_Connor_Conversations_Table — factor 30 - Int_KB_Analytics_Table — factor 1 I then queried each table individually using GET /v1/tables/{tableId} and all three return: rows: 0 indexing: 0 stale: 0 The Conversations records had previously been exported and then deleted from the table. Since the Conversations table has a factor of 30, the reported usage of 990 seems to correspond exactly to 33 previous rows × 30, even though those rows no longer exist and the API currently reports rows: 0. However, both the Usage page and Studio still show 990 of 1K Table Rows used (99%). Could you please confirm whether the Table Rows quota is not being recalculated/released after deleting the rows, and how I can reset the usage? Thank you. https://cdn.discordapp.com/attachments/1556657486579236874/1556657486944010281/Imagen1.png?backend=b2&ex=6ac4f5c2&is=6ac3a442&hm=86a73d6cc42569e55b099879f6d4eeb82b16d426467c773b168740834f2aae4c& https://cdn.discordapp.com/attachments/1556657486579236874/1556657488231792731/Imagen2.png?backend=b2&ex=6ac4f5c2&is=6ac3a442&hm=815341a8faa20fabd1e742989c0d5ba6d59e1e19d1c13d9c16ddb6bed92a9e9b&
d
Yes, the 990 usage is likely coming from previously counted rows in the factor-30 Conversations table, and the quota may not update immediately after deletion. Since the API now reports "rows: 0", "indexing: 0", and "stale: 0", the data itself appears to be cleared. This looks more like a usage/quota counter or recalculation issue on Botpress’ side rather than remaining rows. I can help verify the API responses and determine whether the usage needs to be refreshed/reset by Botpress support.. @early-morning-12731
e
Thanks. I have already verified the API responses for all three tables, and all of them currently return rows: 0, indexing: 0, and stale: 0. However, the workspace still shows 990/1000 Table Rows used (99%). Could you please advise how the usage/quota counter can be refreshed or reset? If this requires an action from Botpress support, could you please escalate or report the issue to the appropriate team? My concern is that the workspace is now very close to the 1,000-row limit even though there are currently no rows stored, which could cause a service disruption.
t
The new billing cycle is what resets it. When I first started using Botpress, I was also under the interpretation that deleting the rows would remove them and get away from the 1k limit. When this did not happen, I noticed either a new billing cycle or purchasing more rows was the solution. Botpress can correct me if I am wrong.
2 Views