Skip to main content
Solved

Why do Products that are already marked as “Offboarding” sometimes revert back to an “In Review” state when a connected Journey is launched?

  • January 8, 2026
  • 1 reply
  • 1 view

It can be confusing when a Product that appears to have completed its Offboarding process suddenly changes back to “In Review” after another connected Journey starts. In Fenergo, this behaviour occurs because the Product’s state machine is automatically re-evaluated when a new Journey is triggered. If the Product still has open review steps or pending tasks, the platform may interpret it as incomplete and reset the state accordingly.

Best answer by jawadkhan

When a Connected Journey launches for a Product already marked as Offboarding, the platform re-evaluates that Product’s state machine. If the Product still has open review steps or unresolved tasks, the state may revert to In Review.

To prevent this behaviour:

  • Complete or verify the Offboarding journey before launching connected journeys.
  • Review your Product State Transition Rules to ensure completed products cannot revert.
  • In Journey Builder, confirm the Product Journey Launchpad task is configured not to trigger for products in Offboarding state.

In earlier releases, this state reversion could occur unintentionally when multiple journeys shared the same entity. This has since been patched - connected journeys now respect finalized Product lifecycles by default.

1 reply

Forum|alt.badge.img
  • Community Manager
  • Answer
  • January 15, 2026

When a Connected Journey launches for a Product already marked as Offboarding, the platform re-evaluates that Product’s state machine. If the Product still has open review steps or unresolved tasks, the state may revert to In Review.

To prevent this behaviour:

  • Complete or verify the Offboarding journey before launching connected journeys.
  • Review your Product State Transition Rules to ensure completed products cannot revert.
  • In Journey Builder, confirm the Product Journey Launchpad task is configured not to trigger for products in Offboarding state.

In earlier releases, this state reversion could occur unintentionally when multiple journeys shared the same entity. This has since been patched - connected journeys now respect finalized Product lifecycles by default.