Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error executing campagin when segment filters added to Strategy



Error executing campaign when Segment filters added to Strategy. When using Segment filter components in a Strategy, the Campaign execution fails.

There are two campaigns, each with a starting Segment of the entire DEV database (1979 contacts). The Strategy sends a single Offer to all members of the starting Segment. For the second Campaign. added a Segment filter component as the first component, referencing a Segment of 10. This follows the configuration in the Pega Marketing User Guide (7.2).

Expected result:
Campaign1: 1979 offers generated
Campaign2: 10 offers generated

Actual Result:
Campaign1: 1979 offers generated
Campaign2: ERROR

Error Messages

Failed to create the batch Data Flow for this Campaign.
Trying to save an invalid page: page is not valid

Following error message thrown during the campaign run was captured in the log file -

(GenerateDF.PegaMKT_Work.Action) ERROR - Error generating Data Flow:
.pyLabel: "P-111_TEST_MyFile_WithSeg__Name__Of__The__Strategy__Or__Name_Of__The__Offer" is too long, maximum length allowed is 64

Steps to Reproduce

  1. Create starting Segment (Seg1)
  2. Create a second Segment (Seg2) that is a subset of the starting Segment.
  3. Create a Strategy (STG1) with a single offer.
  4. Create a Campaign using Seg1, STG1.
  5. Run the Campaign.
  6. Verify Offers have been generated.
  7. Make a copy of STG1 (STG2) using Save As.
  8. Add a Segment filter component before the Proposition import in STG2.
  9. Within the Segment filter component, reference Seg2
  10. Create a new campaign, using Seg1, STG2
  11. Try to Run the second Campaign.
  12. View error message.

Root Cause

This error was caused due to the length of pyLabel exceeding 64 characters.


Suggested to limit the Strategy names or the Offer names used in the Campaign, so that name of the Data Flow which gets created during the Campaign Run does not exceed the 64 character length.

Suggest Edit

Published August 23, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us