Has this update broken anyone else’s configurators? None of ours will fully load anymore without getting an error. Before this upgrade they used API v1 to run User-Defined Configurator methods. Now it looks like they changed it to use API v2, but didn’t update their calls to include an API key. So now, every call to a UD method bricks the configurator. I’m not seeing anyone mention this, so I’m wondering if this is a problem unique to us.
2 Likes