Publishing and testing

Publish a version

1. Save the field schema and settings, then publish from the form editor.
2. Resolve a version conflict by reloading the current configuration before applying the intended change.
3. Confirm that the form is active; a paused form does not accept traffic like an active one.

Test boundary by boundary

1. Send recognizable synthetic values through the installation diagnostic.
2. Find the stored request and compare every field.
3. Inspect recipients, attempts, and provider events separately.
4. Exercise a missing field, invalid address, rate limit, and confirmation path.

A test remains a test

Installation tests are labeled in your inbox. To check email delivery, submit your published form with an address you control and confirm receipt in the destination mailbox.