Help Error Pinterest 201

help fix Pinterest Error 201
I saw a post with a solution but didn’t understand it. can you explain in more detail

Hi @djec,

If a server returns a 201 status, this generally means that the interaction was successful (for ‘created’.) It seems that Pinterests response is sometimes in binary format in which Make module’s cannot be able to parse, so the suggestion is that you might need to add an error handling route

An error handling route will filter out 201 statuses and make sure that the scenario carries on like there is no issue (as there is no issue):
https://www.make.com/en/help/errors/how-to-handle-errors-in-make/overview-of-error-handling-in-make
https://www.make.com/en/help/errors/error-handlers/directives-for-error-handling

Please, follow these steps when asking a question, and you’ll be more likely to get a helpful answer:

:writing_hand: Give us a detailed explanation of what you’re trying to achieve

:footprints: Tell us about any steps you’ve tried so far

:camera_flash: Include screenshots of:

  • your scenario flow and setup (functions, mappings, variables, etc.)

  • module configurations and outputs

  • any error messages you are getting

:card_file_box: Share the blueprint of the scenario you are asking a question about. (this does not contain the connection or personal information)

Henk
Certified Make Expert and Partner
Book a consult with me

1 Like

Welcome to the Make community!

For more detailed error messages, try installing the MDT.

If you have the Make DevTool Chrome extension installed, you should be able to view the request and response headers and body from each module when you manually run the scenario.

From the Help Center article about the Make DevTool:

Make DevTool allows you to debug your Make scenarios in a completely new way. It adds an extra pane to the Chrome Developer Tools. Using this new debugger pane, you’re able to check all the manual runs of your scenario, review all the performed operations and see the details of every API call performed. It also brings a whole bunch of new opportunities for Apps development. You’re able to check every call that your app has performed. Thanks to this extension, you can easily debug your scenario, see which module, operation, even which single response causes the error, and then get your scenario back on track. Try it out and let your scenarios shine!

For more information on how to install and use this, see https://www.make.com/en/help/scenarios/integromat-devtool

samliewrequest private consultation

Join the unofficial Make Discord server to chat with other makers!

2 Likes

I’m using Google Sheets Watch New Rows. If I add a module to ignore error, which module should I add to re-perform the failed operation?