For the complete documentation index, see llms.txt. This page is also available as Markdown.

Run

Understand the tools available on the Run page.

Run is the second phase of the Digibee Integration Platform, following the Build phase. Its goal is to deploy a configured pipeline, run it, and set the integration into production.

Environment selector

Select the target environment in the upper left corner before deploying a pipeline. Two environments are available: test and prod.

  • Test: Use this environment to evaluate and validate your pipeline before moving it to production. You can test and modify its configurations without affecting live integrations.

  • Prod: Use this environment for the final deployment after the pipeline has been tested and validated.

Whenever a pipeline in the prod environment needs an update or a bug fix, make your adjustments in the test environment first, then promote the pipeline back to production.

Environment tag

The environment tag helps you identify which environment you are working in, preventing accidental actions in the wrong environment. The tag color indicates the criticality of the selected environment:

  • Production: Pink

  • Test: Light blue

The tag is displayed on the Run page, the Monitor page, and in the Consumers (API keys) settings page.

Auto refresh data

The auto refresh function automatically updates page data at a selected interval:

  • 5 seconds

  • 10 seconds

  • 30 seconds

This option is enabled by default. To disable it, select Auto refresh off.

Projects list

After selecting the environment, select the project you want to deploy. Projects are listed below the environment selector.

As you interact with the Run page, additional data loads progressively in the background. This infinite scroll mode is designed to display essential content quickly.

Read the Projects documentation for more details.

Global search and filters for deployed pipelines

You can search for deployed pipelines across all your projects using keywords from the pipeline name, in both test and production environments. Search results display the pipeline name, the associated project, and all available versions of each pipeline.

You can also filter pipelines by:

  • Status: Filter by the pipeline's current status. Available options are: Deployed, Error, Redeploy, and Starting. See pipeline statuses for more details.

  • Triggers: Filter by up to five selected triggers.

See pipeline versioning for more details on version management.

Deployments

All pipeline deployment information is available in the center of the Run page. You can view it in two display modes: Blocks and Table. To switch between modes, use the toggle in the upper right corner of the screen.

Pipeline options

To access advanced options, click the three-dot menu on the selected pipeline:

  • Promote to: Moves the pipeline to another environment.

  • Redeploy: Redeploys the same pipeline with configuration changes applied.

  • Rollback: Reverts the pipeline to the previous successfully deployed version. Use this option when errors occur after deploying a new version.

  • Remove deploy: Removes the deployment for the selected version only. Other versions are not affected.

  • Open canvas: Opens the executions page in Monitor.

  • View executions: Opens the executions page in Monitor.

  • Open differences between versions: Allows you to compare two minor versions of deployed pipelines side-by-side.

Deployment

Click Create New to choose a pipeline to be deployed. In the screen you will select:

  • Pipeline name

  • Pipeline version

  • Project

  • Instance

  • Engine version

  • Pipeline size

  • Number of concurrent executions

  • Number of replicas

Check out the Deployment documentation for more details on how to deploy a pipeline, how to promote pipeline across environments, and more.

History

To track recent pipeline changes and review what has been deployed, open the History tab in the deployment details sidesheet.

Next steps

Now that your pipeline is deployed, read Monitor to follow data and track how your pipeline is performing in real time.

Last updated

Was this helpful?