Hi @tstachlewski
Thanks for responding. It’s turned out the behaviour is not quite how I described.
When I Add a new Post, if it works properly, the player and the sound file are added to the post as expected.
However, most of the time, when I click Publish the server throws a 503 error and times out. When i refresh, the post has published and the player is loaded onto the post but the sound file doesn’t arrive in the S3 bucket. Given the server timeout error, I assume it’s at the plugin level. Something in the Polly plugin process seems to be causing trouble with the server. Given this is an RSS file with some identification meta data, I’m not sure why it would bog the server. (The AWS flow chart shows it going to AWS Lamba, then to the Polly service for processing.)
If it does work (only twice now on the live server), when I Update the post, it reprocesses the sound file and updates it too. It doesn’t have a problem redoing the file, just publishing it the first time. If it doesn’t work, it doesn’t cause it to work during an Update.
After announcing the new feature on my blog, i was obliged to turn it off. The plugin has updated twice in the last few days but the fixes don’t seem to be related.
i spoke with my Hosting service and they don’t know anything at their end that would get in the way.
The only other plugin that processes on Post is “WP to Twitter.” It announces new posts on my Twitter account.
What I’m interested in is:
a) a way to manually trigger Polly processing on an existing post so that if it didn’t work, i can re-trigger it. This would make fixing and testing much easier. (ie: a button on the New Post Polly plugin section.) Don’t know enough about how it works to know how difficult this would be.
b) any suggestions on how i get Polly working reliably.
Thanks!