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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment