Register an application's query recipes at deploy
What It Does
An application deploy submits recipe declarations after its datasets are registered. Custom-object recipes follow workspace object activation rather than an application release.
The Flow
Submit the application recipes through the synchronous registration function. Check each template and join against registered dataset metadata, rejecting workspace-only fields and changed content with an unchanged version. Replace changed recipes, retire omitted ones and reactivate returning declarations in one transaction.
When Something Fails
Invocation failure stops the deploy. A failed invocation does not by itself prove whether a prior write committed. Return all collected declaration problems without applying the release. The previous recipe release remains. Rollback the recipe write on failure. No partially applied recipe release is retained by that transaction.
Idempotency and Concurrency
Repeating unchanged declarations requires no recipe replacement or release-version change. Recipe validation precedes one transaction for the application manifest; different application declarations retain separate ownership.