hasura action gives error on changing parameters

Version Information

v2.14.0-cloud.1 Server Version: CLI Version (for CLI related issue):

Environment

Cloud

What is the current behaviour?

Getting this error on an action, despite not setting any custom response transformation on my own. In the Actions settings tab, there isn’t any added request transformation. This action used to work perfectly before, but started giving errors recently. Now, any new action faces the same errors. From the logs I know that the request is properly handled at the backend (webhook that the action calls). This “Response Transformation” error started appearing out of nowhere as far as I know.

What is the expected behaviour?

For this to not happen, and the action to be processed properly.

How to reproduce the issue?

1. In the account I’m using, first, make an action with say any parameters.
2. Set everything properly. Test the action. It works perfectly. Now, go to the action settings and change anything, for example, add a new parameter to the action.
3. Test the same action. would crash with this error.

Screenshots or Screencast

Here is also a screencast of me reproducing the same issue on a new action. The code for the testingAction webhook is simple:-

module.exports.testAction = async (req, res) => {
  console.log("hit")
  return res.json({
    status: "Banana"
  })
};

I do get a “hit” printed in the logs, even after the response doesn’t show up properly on hasura.

https://user-images.githubusercontent.com/111136776/199655968-4b4d8ba6-d5b5-429f-ac00-0796eb8fd109.mp4

Please provide any traces or logs that could help here.

Any possible solutions/workarounds you’re aware of?

None

Keywords

“Response Transformation Failed”

[BenoitRanque]

@arush-spacetime you can fix the old action with the following steps:

• export metadata from the console as a json file
• find the json key response_transform in your action metadata and remove it for all affected actions
• import the metadata from the console back into your project

This assumes you never had a response transform, which should be the case for most users.

[tirumaraiselvan]

@cheets I think you may have to clean your old actions as mentioned in this comment. Also, pls hard refresh your browser to load the new assets from the CDN.