Loading

Salesforce Loyalty Management: Flow error when invoking runProgramProcess action element for Change Tier Assessment

Udgivelsesdato: Jul 8, 2026
Beskrivelse

This article answers why Flows in Salesforce Loyalty Management fail when invoking the runProgramProcess action element, and how to resolve each root cause. It also covers the related mergeLoyaltyProgramMemberships parameter error.

Administrators and developers who build or maintain Loyalty Program Process Flows may encounter these errors during execution:

• "We couldn't run action [action name] because something went wrong. We couldn't execute the change tier action element of the runProgramProcess type. Review your action name and version."
• "This parameter is missing from the action. To avoid errors when running this flow, delete this value or restore the parameter."

These errors affect Flows that invoke Loyalty Program Processes such as Change Tier Assessment or other tier-related processes in Salesforce Loyalty Management. The runProgramProcess invocable action runs in the context of the triggering user, so permissions, action configuration, and data quality all affect execution.

Common causes include insufficient user permissions, an incorrect process name or version reference in the Flow, changed action parameters, Transaction Journal data that does not meet program rule criteria

Løsning

Review each section below and apply the fix that matches your error symptom.

1. Insufficient Permissions for the Running User

The runProgramProcess action executes as the user who triggers the Flow. If that user lacks the required Loyalty Management license, permission sets, or object access, the Flow fails with: "We couldn't execute the action element of type runProgramProcess."

Step 1: Verify the user's Permission Set License.

1. Go to Setup, then Users, and select the affected user.
2. Under Permission Set License Assignments, confirm the user has an active Loyalty Management Permission Set License (PSL).

Step 2: Verify required Permission Sets.

1. Go to Setup, then Permission Sets.
2. Confirm the user has all of the following assigned:

- Loyalty Management

- Manage Loyalty Program Processes

- Any custom permission sets granting access to Loyalty objects

Step 3: Verify Field-Level Security.

1. Go to Setup, then Object Manager, then select Loyalty Program Process.
2. Open Fields & Relationships and confirm the running user has Read access to all required fields.
3. Repeat this check for Transaction Journal, Loyalty Program Member, and Loyalty Program objects.

Step 4: Verify Record-Level Access.

1. In Object Manager, open Loyalty Program Process.
2. Confirm the user can access the specific Loyalty Program Process record referenced by the Flow.

Step 5: Isolate the permission gap.

1. Run the Flow as a System Administrator.
2. If it succeeds, progressively reduce permissions on a test user until the missing access is identified.

2. Incorrect Action Name or Version in the Flow

If the Flow references a Loyalty Program Process by a wrong name or inactive version, the error reads: "Review your action name and version."

Step 1: Confirm the correct API Name.

1. Open App Launcher, navigate to Loyalty Management, then Loyalty Program Processes.
2. Locate the target process (for example, Change Tier Assessment).
3. Note the exact API Name and confirm the process status is Active.

Step 2: Update the Flow action reference.

1. Go to Setup, then Flows, and open the affected Flow.
2. Select the runProgramProcess action element.
3. Confirm the Process Name input exactly matches the API Name noted in Step 1. This value is case-sensitive.

Step 3: Resolve version conflicts.

1. If multiple versions of the Loyalty Program Process exist, ensure only one version is Active.
2. Deactivate any obsolete versions to prevent conflicts.

Step 4: Save and activate the Flow.

3. Missing or Changed Parameters in Invocable Actions

When an invocable action such as mergeLoyaltyProgramMemberships shows: "This parameter is missing from the action. To avoid errors when running this flow, delete this value or restore the parameter," the action's metadata has changed since the Flow was last saved.

Step 1: Open the affected Flow and select the action element showing the warning.

Step 2: Remove all existing input assignments from that action element.

Step 3: Delete the action element entirely, then re-add it.

1. Search for the action by name (for example, mergeLoyaltyProgramMemberships).
2. Re-adding the element reloads the latest parameter schema from the org.

Step 4: Re-map all required input values to the refreshed parameters.

Step 5: Verify the Flow API Version.

1. In Flow Builder, open Flow Properties.
2. Confirm the API Version matches the current Salesforce release. Updating to the latest version ensures the Flow uses current action metadata.

Step 6: Save and activate the Flow, then test execution.

4. Transaction Journal Data Does Not Meet Program Rule Criteria

The runProgramProcess action evaluates Transaction Journal records against Loyalty Program Rules. If the data does not satisfy rule conditions, the process exits without completing and may surface a generic action error.

Step 1: Open the Loyalty Program Process in Loyalty Management and review the rule criteria configured for the process.

Step 2: Open the Transaction Journal record used in the failing Flow run and verify each field value matches the expected rule criteria (for example, Journal Type, Transaction Amount, and associated Loyalty Program Member).

Step 3: Correct any mismatched data on the Transaction Journal record or adjust the rule criteria to match valid data, then re-run the Flow.

Vidensartikelnummer

005388656

 
Indlæser
Salesforce Help | Article