•Checkpoints

Checkpoints are snapshots of the project's state.

They serve three purposes:

• A package management solution that allows you to create and share Arbiter projects
• A version control system used for tracking and managing changes to project
• Workflow compilation that performs various checks before deployment

•Artifacts

Artifacts are all of the resources packaged by the build process upon checkpoint creation. You could view the state of the artifact in the specific version or restore the artifact's configuration if needed.

Artifacts types are:

• Workflows
• Connectors
• Processors

•Compilation errors

Compilation errors happen when you have an invalid configuration or a mismatch in acceptable types.

•Example

1. Let's deliberately remove productId from the Start node. As you can see GetProduct and PlaceOrder connectors depend on it.
2. Let's mess around with the result and change the type of the field message from Text to Number
3. After creating a new checkpoint you could see that checkpoint's Status is Failed and there are four errors(Compilation errors tab)

•Checkpoint Export

You could easily export the checkpoint which represents the compiled project. The resulting file is in JSON format that you can store or share. For importing checkpoints see here.

•Deployment

You can deploy a version of the project to production only from a checkpoint. When you select the Deploy button you'll see a configuration flyout. From there you have to choose for which workflows you want to include state data in task history and you will have to populate environment variables if your project uses one.