Forum Discussion
AI Text-to-speech no voices today
Hi Everyone,
We've identified the issue that caused delays when accessing AI Audio features in Storyline 360 and Rise 360.
We're starting to see recovery across AI Audio in Storyline 360 and Rise 360, as well as other AI Assistant features. Some Creators may still experience delays while recovery continues. We're monitoring progress closely and will share another update as soon as we have more information.
The Articulate status page is a great way to see the current status of all Articulate services. If you'd like to stay updated, please click the SUBSCRIBE button in the upper right corner of the status page, so you can receive notifications of any changes.
Again, we apologize for the disruption and thank you for your patience!
Since Articulate won't respond I think I've discovered the issue. Storyline did an update on Monday, June 9. It was working fine for me in the office that day. I didn't update until Tuesday. I was working from home that day and yesterday so didn't see this issue. I"m back in the office today. I ran a diagnostic and looked through the error log and found the culprit.
Our firewall blocking the AI calls when using Storyline becuase they added new AI features and it's trying to connec to new subdomains that aren't whitelisted by our IT.
Here's a brief summary.
Technical Details & Log Symptoms:
- The Storyline client attempts to fetch arrays from endpoints like https://articulate.com.
- Instead of the expected JSON data, the corporate firewall/proxy intercepts the request and injects an HTML/JSON error page (containing a statusCode key).
- Storyline tries to deserialize this error response into an internal data type (ManifestListContainer), causing a crash with the following error:
Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'Articulate.ThreeSixty.Core.Internal.ManifestListContainer'1[Articulate.ThreeSixty.Core.Internal.TeamFolder]' because the type requires a JSON array... Path 'statusCode', line 1, position 14. - This is followed by a cascade of Network request failed... A task was canceled errors for the AI voice endpoints.
I imagine this issue is probably affecting many other users with strict IT firewall enforcement policies. Articulate should've anticiapted this when they added all the subdomains for these new AI calls. Very frustrating. It will take hours, maybe a few days who knows, for our IT to get these whitelisted. Meanwhile, my 15 courses I'm building that already have the text-to-speech build on every single slide. I can't edit them or add new ones.