Skip to content
English
  • There are no suggestions because the search field is empty.

Why do I have to keep reactivating the flow?

When you create and activate a flow on a version or publication in the Mavim Portal, the system automatically copies the flow to any newly published versions of the same definition. However, the copied flow is not active by default. This is because new publications first have the approval status. Only after switching from approval to online can the flow be activated. This manual step is required to keep flows under control and aligned with the approval cycle.

How to activate a flow on a new version

  1. Log in as an Administrator in the Mavim Portal,

  2. Select the Flows tab.

  3. Find and select the version where you want to enable flows.

  4. Check the box Enable processing for this version.


Best practices for managing flows

To avoid issues with performance and control, keep these guidelines in mind:

  • Flows are linked to a specific version
    Always disable flows for versions that are not needed. For example, if a new version is online but the old version must remain available, ensure only the required version has active flows.

  • Only create flows when necessary
    Each flow should have a clear purpose with a defined trigger and output. Ambiguous flows can cause loops and slow down the system.

  • Use clear triggers
    Always document the use case for each flow. This makes it easier to manage and troubleshoot later.

  • Spread out time- or date-based triggers
    If too many flows run at the same time, memory limits can be exceeded, leading to system slowness. Schedule flows so the load is distributed over time.

  • Plan execution for large-scale flows
    When running flows on large data sets, stagger the triggers to reduce peak load.

  • Inactive versions do not run flows
    Flows linked to versions that are offline will not execute.


Summary

Flows must be manually reactivated on each new publication version after approval to maintain control and prevent unintended executions. By following the best practices above, you can keep flows efficient, stable, and aligned with your publication needs.