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 run completed but no output to DB and CSV

SA-60800

Summary



A campaign is run on a weekly basis (every Monday) in the Production environment. This campaign sends an SMS and outputs the result to a database and CSV. 
Post completion of the campaign, output records were not sent to the database and CSV.



Error Messages



Not Applicable


Steps to Reproduce



Schedule a campaign to run on a weekly basis.


Root Cause



An issue in the custom application code or rules.

Debug was enabled on 'PegaMKT_Work_ProgramRun'. As a result, the database reported connectivity time threshold breaches and PEGA0026 alerts when the campaign was run. Hence, FileDBSchedule did not run. It was responsible to perform the scheduled finalization for the File and Database output channels.


Resolution



As a local-change, restart the environment.


 
Suggest Edit

Published July 23, 2018 - 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