Hi @Leon thanks for the question, let me try to clarify the behavior.
When an ingestion is requested, QS cannot accurately estimate the size of the dataset, therefore, the logic is to start ingestion as long as there are >0 capacity left. We would only know the size when ingestion is finished, which might already have been several hours. With that logic, it is possible that the final used capacity exceeds the purchase capacity. For user friendliness, QS still allows that as an exception path. But all the following ingestion will be failing since there are no purchased capacity left.
Please note, if this (over capacity) happens, we WILL charge for the actual usage, rather than the purchased capacity. If users want to enforce the limit, the admin will have to delete the dataset. Or the admin needs to purchase more SPICE capacity to avoid further ingestion failure.
Please let me know if further clarification needed. Thanks!