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

Campaign Recurring Run Date Issue for 29,30,31 dates



Users cannot configure a Campaign to run with a recurring schedule for Monthly runs on 29, 30, 31 dates. Product assigns future run dates for all months with the same date and then date validation raises errors saying those dates do not exist for some months.
For example, on 31 May we configured campaign to run Monthly for 3 months and it set future run dates as 31 June, 31 July, 31 August. 31 June is a non existent date and campaign raised errors when you click RUN campaign

Error Messages

The Flow Action pre-processing activity PreSubmitForExecution failed: value 20170631T133031.990 GMT is not a valid Date or DateTime string. Details: Invalid value for theDate passed to com.pega.pegarules.exec.internal.util.PRDateTimeUtilsImpl.addToDate(String, String, String, String, String)

Steps to Reproduce

1. Configure a campaign with Monthly recurring schedule.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-35081.

Published June 20, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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