we have a number of configurators based on the same Grasshopper definition.
Everything works fine, except that if for some reason a given combination of parameters results into a temporary failure (maybe a timed-out computation or texture loading error) then the same combination of parameters will not be recomputed again and will alsways return an error - like if it is a cached result.
(something already mentioned here: https://discourse.mcneel.com/t/broken-model/124924/5 )
This obviously doesn’t work, especially when the parameters combination is the default one.
In the above mentioned thread, you indicated that re-uploading the definition was the only solution for clearing the cache, but since re-uploading the definition also changes the embed ticket, this requires to update all the configurators that are based on that definition.
Also, there is always the possibility that a computation fails in the future, so if that “failure” is stored as a “solution” the same problem can occurr again.
Right now, the only solution that I can think of in order to clear the cache, is to create a local table with locally defined configurator IDs associated with embed tickets, so that we can re-upload the models and update the tickets only in one place, but this would not solve the main issue of the cached failed results, and I don’t think there is a way of knowing if/when a model has failed.
Am I missing something? What can we do to solve this?
Thanks in advance,