Test, dry-run and apply

Nothing a connection describes is made until you press “Apply”. Before that, one press of “Check it” runs two stages, a test and a dry-run, and shows you “Here’s what will be created”. The step-by-step wizard and the canvas check and apply a connection the same way.

Test

The test runs every step’s script in your own browser. Nothing is sent over the network, and nothing is saved. Each script gets 1 second; a script that takes longer is stopped. A step without a script is built from its fields.

The test shows each step’s result. When a step fails, it says why, and “Fix” takes you to that step.

“Try it” runs a test for one script on its own, with the sample input you give it, and shows what that script returns. It is the quickest way to see what a script does while you write it.

Dry-run

The dry-run runs only after a passing test. It asks Lingara whether every object the connection describes would be accepted, using the same checks as creating it by hand in Developer tools. It writes nothing.

“Here’s what will be created” then lists each object with what will happen to it: new, changed, no changes, replaced, or can’t be made. When something can’t be made, the reason is beside it, and nothing can be applied until you fix it and check again.

Apply

“Apply” makes or updates the objects in order and shows each one’s progress. Each new password is shown once, as it is made: copy it before you move on. Lingara records everything it made in the connection.

If apply stops partway, the connection keeps what was made. Fix the problem, check again, and the next apply carries on from where it stopped.

Changing a connection later

Open a connection again to change it, check it, and apply again. Only what changed is updated. If you change where messages go, Lingara makes a new webhook endpoint with a new password, and removes the old one afterwards.

Editing anything clears the last check, so “Apply” waits until you press “Check it” again.

Objects you made by hand in Developer tools are never pulled into a connection. Deleting a connection leaves what it made working, and you can still find it in Developer tools.