Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Pausing background processing

Updated on June 25, 2021

To avoid inconsistencies and data integrity issues during the manual import, pause any background process that might trigger the running of rules before the update is complete. Otherwise, the application might start running rules before the new rule base is consistent and ready for use.

Review the following background processes that are provided and active by default, and that might be in use by your application.

TypeProcessDescription
Agent (Standard)PegaCLMFS:FSEventQueueConsumerProcessing of EDA events
Agent (Standard)PegaCLMFS:CreateCustomerReviewEventsIdentification of customers subject to customer review due to the next review date
Agent (Standard)PegaCLMFS:CreateCustomerDocExpiryEventIdentification of customers subject to customer review due to expiration of documents
Agent (Standard)PegaCLMFS:GenerateAndAttachPDFGeneration and attachments of PDF file representation of KYC questionnaires
Job SchedulerRNGCreateCustomerDocExpiryEventsIdentification of customers subject to customer review due to expiration of documents (2G)
Queue ProcessorRNGDMSOutboundSyncPropagation of document metadata to external DMS systems
Queue ProcessorAsyncProcessingBackground execution of cases queued for asynchronous processing (immediate)
Queue ProcessorAsyncProcessingDelayedBackground execution of cases queued for asynchronous processing (delayed)
Queue ProcessorSyncUpPointSynchronization and data propagation of Group Management cases after completion of related cases
Queue ProcessorSPUCoreDetection of changes in regulatory rules and propagation to cases (SPU)
Queue ProcessorSPUMasterDetection of changes in regulatory rules and propagation to cases (SPU)

Consider any other background process or inbound flow that your organization might have implemented and that might trigger the execution of logic. For example, processes of this type might be the remote creation of cases through Pega API or the reception of events through data flows.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us