Overview

This article covers how to resolve a known bug where mandatory or non-mandatory activity settings are not updating correctly in Journeys.

Understanding the Mandatory/Non-Mandatory Activity Bug

A known bug in the system causes changes to an activity's mandatory or non-mandatory configuration to not update correctly in the backend Journeys table. This occurs when an activity is initially saved as mandatory and later changed to non-mandatory, or vice versa. In these cases, the system continues to follow the original configuration rather than the updated one.

Note: This is a known product bug. The workaround below applies until a permanent fix is deployed.

Workaround: Recreating the Activity with the Correct Configuration

To resolve the issue, identify the activity with the incorrect configuration and delete it. Recreate the activity with the same details and set it as mandatory or non-mandatory at the time of creation, as required. This ensures the configuration is stored correctly from the outset.

Confirming the Workaround Has Resolved the Issue

After recreating the activity, save the changes and verify that the mandatory or non-mandatory status is set as expected in the workflow. Test the activity by attempting to skip it (if non-mandatory) or proceeding without completing it to confirm the expected behavior. If the issue persists, provide details to Freshworks Support for further assistance, referencing the known bug associated with the Journeys table.