Maximum allowed computation time was exceeded


we have a private model embeded in our application which is used extensively. During this period from 10:00 a.m. to 6:30 p.m. approximately, our users repeatedly experience this type of error in attachment 2020-10-28_19-11-29 except that in my application no error is caught and this results in an empty scene or with missing geometries, users are forced to refresh the browser page (this leads to the loss and creation of many paid shapediver sessions). On other less used models this error never occurs.
This renders our app unusable and we lose users who are frustrated. Can you look what it is, this is model pcl-v1-6-5-sd01


Your model is a great great example of a paramteric online application. Since it has lot of parameters and features, the computation time is around 10 seconds which is the limit of your account right now. PRO customers use the ShapeDiver shared system where performance fluctuations can occur and computation time might exceed for models that are near the limit as it happens in your case. Read more about computation time in here.

There are two ways to solve this:

  • You can either optimise your model to decrease the processing time and stay within safe margins of your time allowance. Optimisation techniques are well covered in this blog post, video tutorial and the webinar.
  • Or you can increase your computation time limit. If you are interested in upgrading your account please contact sales via the contact form at


I’m aware about the optimization, because we did them since 2 years we created the first version.
I did one test on 2 minutes ago. I change the parameter POINTURE from 38 to 42, the error message (mximum allowed computation…) is directly appeared.
I would like that error appear around at least 10 seconds after the text input changed.

Furthemore, as I said there was’nt this kind of issue 10 days ago.

Thanks for your help

The message can pop up immediately if the solution for given parameter set timed out and has been already cached.

We haven’t recently pushed any updates that could affect computation time. I’m wondering if there is anything that has changed on your end. Does this happen to old models or only to the latest uploads?

This model has been uploaded on august 25th. There was sometimes timeouts (in some particular cases), but not as much as these last 10 days.

We have other models recently uploaded, but less used by our customers and without issues of this kind.

I have reset the cache of the model and cleared all saved solutions including those which timed out. Change of parameter POINTURE from 38 to 42 works fine but please give it a go with other settings and let me know if this helped.

I did some tries on app.shapediver and on our own app. I didn’t encountered the issue.

I hope to have feelings of my customers about their utilization this end of afternnoon and then I will tell you if your action has eradicate this problem

Thank you!


It seem’s the problem is back again.
Could you tell me what you see and if old sessions could/should be cleaned ?

Thank you

I cleared the cache again and you shouldn’t get any errors now. I will keep an eye on the model in following days to make sure it runs smoothly but please let me know if that’s not the case.

Hello Pavol,

I think, after some tries that the problem is slowly coming back again. Don’t know if it can be visible on your side (with logs or else)


Your model is at the limit of your computation time allowance so any warnings you get are expected. As I mentioned earlier, you can either optimise your model further or upgrade your account to increase the computation time to 30 seconds to solve this issue.

What I don’t understand is why the problem only arises when there are a lot of open sessions on the same model.
Are the 10 seconds shared between all the sessions open at the same time and which require computation time if the modified parameter is not yet cached (knowing that there is rarely any cached data which can be shared between sessions, as we have an import parameter of an obj file which is unique per client that initiates the session of a model)

Thank you.

Each session gets the allowed computation time. Otherwise busy models would get a progressively worse performance and we wouldn’t build a platform like that, would we :wink:. Learn more how our scalable infrastructure works in the last section of this article.

However, any inconsistencies in performance you experience may arise from the OBJ import which is unique for each client. It’s worth looking into how dense the meshes are and maybe optimise them prior the upload to ShapeDiver. This could reduce the computation time your model needs for processing the OBJs and stay within the limit.