Why did Trustpilot HTTP call return a 403 error, and how can I access response body and headers?

This topic was automatically generated from Slack. You can find the original thread here.

I received a notification from a Workflow to say that a Trustpilot HTTP call returned a 403 error.

  1. When I click the link to inspect the event (from Slack), Pipedream shows an error message saying the event ID can’t be found, but then proceeds to list out the steps output for that event.
  2. When I look at the last step in my workflow, I can see it’s the last HTTP call to Trustpilot that’s returning this 403 error. However, I am not able to see any other response information other than the code. Can I see the response body and headers? How?

Also, how can I retry a specific failed workflow? I’d like to just try the call again in case it was a temporary error at Trustpilot.

Hi , may I ask how do you call the TrustPilot? Are you using a code step or the build in action?

About the event link in the notification, I will try to reproduce that

Shall I provide the event ID for you to look into?

Hi , I afraid I can not access your account. If you can share a screenshot of your action then that would be a great help for me to help you. Or you can try to ask our bot @U05A7KLNALC

I understand that you’re facing a 403 error with the Trustpilot HTTP call and having trouble viewing the event details. To help you better, it would be great if you could share a screenshot of the action or provide more information about the steps in your workflow. Regarding retrying a specific failed workflow, you can use the $.flow.rerun method in a code step to rerun the workflow from the beginning. You can find more information on how to use this method in the Pipedream documentation. If you still face issues or need further assistance, please don’t hesitate to ask more questions or provide additional information.

Is it not possible to retry a step from the event log / history page using the Pipedream UI?