Genesys Cloud - Developer Community!

Hi,

We are currently troubleshooting a Web Services Data Action that has been working great for a while but suddenly started failing today. The endpoint returns, upon a correct request of course, a 302 response code with location header pointing on another endpoint where the actual result will be returned. The data action has previously followed that redirect to the other endpoint and successfully retuned the data. Starting today execution of that data action fails. We know from reviewing logs on the endpoint that the 302 is still being sent, but no request is sent to the other endpoint.

Can you clarify if there has been any changes to the data action integration (non listed here) and also on the expected behavior on following 302's? I can't find any information about that in documentation or previous posts.

Best regards

Jonas

Sorry, this was unintentionally broken for a few days. The latest update to the data action service was rolled back, so your data actions should be operational again. In general an issue like this should go to support, as the forums are not really intended for bug reports.

I reported this to support as well but their initial response was, as usually, to blame it on an external part. They said the endpoint sending the 302 did not provide a location header, and thus they did not escalate to development. Not until after the rollback was done where we informed about this.

Btw, the release notes were not updated about this release. Can you make sure you update this, makes it easier for us to troubleshoot.

There wasn't a known or intentional change to 302 processing, so we did not include it in the release notes. Unfortunately our existing 302 processing tests did not catch this change in behavior. This was also rough for support to diagnose as the error message that was returned was misleading at best. We now understand the issue and will have it resolved along with new tests for this scenario prior to deploying this change again.

Updates to the release notes are reserved for new features or significant / "breaking" changes in behavior. We typically deploy a new version of the data action service every week for security updates and other small changes, which we do not update the release notes for.