Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.2.0f3
Issue ID
958652
Regression
No
Publish does not fail when hitting usage limit before upload starts
1. What went wrong?
When making a commit via Collab that will either reach or exceed the tier-specified usage limit of the user's Organization then the publish is allowed to finish uploading the commit before the publish itself fails, returning with an orange error telling the user that they need to manage their usage. If the user is trying to make a large commit (2GB+) then they'll be forced to wait for the files to be uploaded first before the service returns with a failure, notifying them that their time was wasted until they manage their space first.
2. How can we repro the issue?
a) Create an org with that has Free or Standard Teams seats. Assign one of those seats to yourself.
b) Create a new project and add enough assets to get close to but not exceed the usage limit (1GB for Free, 25GB for Standard).
c) Add enough assets to reach or exceed the usage limit, then publish them via the Collab Toolbar.
Expected: Before the upload phase of the publish starts the entire publish should fail immediately with the orange error message telling them to manage their usage.
Actual: The upload phase needs to complete before the publish returns with the orange error.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
Add comment