In case you recompute the solution, does this problem happen again? It could be a temporary connection problem to the ShapeWays API.
We experienced that the ShapeWays API can get slow sometimes, which impacts user experience for your models on ShapeDiver. We therefore suggest for now to use the components for requesting materials, categories, and printers from the ShapeWays API for model setup only, and then hardcode the material and category IDs into your Grasshopper model.
Our ShapeDiverShapeWaysPrice components, which uses the ShapeWays API to retrieve a price estimation, can suffer from the same problem of slow API access. We are thinking about an alternative solution to this.