I’m getting a new error thrown back when trying to send a model up to the our workspace that says Workspace limits have been reached. I’ve tried poking around the workspace config to see if there was any parameters for versions/models/projects but I can’t seem to locate anything. I noticed we have exactly a 1000 versions so I’m guessing that might be the limitation marker.
Here is the full error message:
GraphQLException: Failed to execute the GraphQL version request. Errors: [{'message': 'Workspace limits have been reached', 'locations': [{'line': 3, 'column': 5}], 'path': ['data', 'data'], 'extensions': {'code': 'FORBIDDEN', 'statusCode': 403}}]
I did discover the admin mutation for updateWorkspaceLimits and gave that try from the explorer, but it looks like the admin permissions I have isn’t enough to run any admin queries/mutations.
I imagine that new limit will be hit sooner or later (hopefully not soon ) so I setup a simple script that checks our workspace metrics twice a day and notifies our team if we’re close to the limit.
As a side question - if a limit is hit in our workspace, will that block any inbound models sync’d from acc? Or does it get put in a queue and sent over there is room?
We’ve significantly increased the limit, so you’re unlikely to hit it anytime soon, no need to worry.
If the limit is ever reached, any inbound model sync will be blocked. This safeguard exists because some users accidentally, or in some cases abusively, send thousands of objects (sometimes empty) programmatically.
thanks for that info @Nikos! We’ll have to make sure this script keeps an eye on things then. We are still in the early phase of sending projects into speckle, but I even with only a few projects we have around 10-40 models in a single project that are getting synced over daily. That could grow quite fast once we port all 200+ active projects in acc
