DEPRECATED Reset an automated recipe from its template

Deprecated: use POST /api/v3.1/automated-recipes/{recipe_id}/resetup/. This version stays available until it is switched off; see Moving recipes to v3.1.

When the recipes service fails, this version answers 500 with an HTML page, and an error in the 4xx range can arrive with a body that is not JSON. It also repeats the request to the recipes service up to three times, create included, so a create can run twice. v3.1 does neither: every error is {code, message, details}, and a request is repeated only when it provably never reached the service.

Rebuilds the recipe from the template it was created from, and starts the build. Every recipe in the dependency tree is snapshotted first, then their cells are dropped and recreated from the current template.

This is how a fix made to a template reaches the recipes already deployed from it. The existing configuration - data sources, connections, accounts, sync_from_date - is preserved, and unlike a configuration PUT the build does not have to be triggered separately afterwards.

Takes no request body. A 200 means the reset was accepted and the build was started, not that the build will succeed - as with POST /build/, a failure arrives asynchronously in the error field of the recipe detail.