Skip to content

Adds known limitations for MxPipelines #10708

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
OlufunkeMoronfolu wants to merge 1 commit into
base: development
Choose a base branch
from
Draft

Adds known limitations for MxPipelines #10708

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions content/en/docs/deployment/general/mendix-pipelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -338,11 +338,13 @@ Mendix automatically creates a webhook on your behalf to trigger Mendix Pipeline

### Known Issues and Limitations

Mendix Pipeline runs are not picked up and executed if the Mendix Pipelines functionality is undergoing maintenance.
* **Mendix Pipelines maintenance behavior** – Mendix Pipeline runs are not picked up and executed if the Mendix Pipelines functionality is undergoing maintenance.

It is not currently possible to add the same Mendix Pipeline step more than once in a Mendix Pipeline. This will be improved in the future.
* **Duplicate pipeline steps not supported** – It is not currently possible to add the same Mendix Pipeline step more than once in a Mendix Pipeline. This will be improved in the future.

In case of a system outage, Mendix Pipelines triggered during that time are not executed.
* **System outages prevent pipeline execution** – In case of a system outage, Mendix Pipelines triggered during that time are not executed.

* **Pipelines continue to run after app offboarding** – If an app is offboarded while pipelines are still configured, they will continue to run on their automated schedules and generate failure notifications. To prevent this, active pipelines must be deactivated during the app offboarding process, before the app is removed.

## Read More

Expand Down