# PEGA0011 alerts in production **URL:** \ **Category:** General\ **Tags:** communications-and-media, pega-diagnostic-center, 8-4, decision-management, decisioning-architect, system-administration\ **Created:** [March 24, 2023, 10:24am UTC](https://forums.pega.com/t/pega0011-alerts-in-production/4221 "2023-03-24T10:24:23Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![prasadn1](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@prasadn1](https://forums.pega.com/u/prasadn1)\ **Post date:** [March 24, 2023, 10:24am UTC](https://forums.pega.com/t/pega0011-alerts-in-production/4221/1 "2023-03-24T10:24:23Z")
Hi All, We are getting pdc PEGA0011 alerts in our production. While searching in logs we are able to see only service activity name in logs. Please help me to get this issue resolved. Please find the logs in the attachment. We are getting PEGA0020 alerts along with this. [PEGA0011.docx](https://forums.pega.com/uploads/short-url/vO5tAEERuv1lceOlJDJhgGc8gxl.docx) (14.5 KB) ---
**Author:** ![MarijeSchillern](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marijeschillern/32/23321_2.png) [@MarijeSchillern](https://forums.pega.com/u/MarijeSchillern)\ **Post date:** [March 24, 2023, 11:58am UTC](https://forums.pega.com/t/pega0011-alerts-in-production/4221/2 "2023-03-24T11:58:47Z")
@prasadn1 can you confirm that you carried out troubleshooting suggestions provided on the [Predictive Diagnostic Cloud](https://support.pega.com/predictive-diagnostic-cloud)pages? [Event Viewer landing page in Pega Predictive Diagnostic Cloud](https://docs.pega.com/bundle/predictive-diagnostic-cloud/page/predictive-diagnostic-cloud/reference-guide/event-viewer-landing-page-in-pega-predictive-diagnostic-cloud.html) [Identifying top performance issues in your system with Pega Predictive Diagnostic Cloud](https://docs.pega.com/bundle/predictive-diagnostic-cloud/page/predictive-diagnostic-cloud/reference-guide/identifying-top-performance-issues-in-your-system-with-pega-predictive-diagnostic-cloud.html) [PEGA0011 alert: Total request time exceeds limit](https://docs.pega.com/bundle/predictive-diagnostic-cloud/page/predictive-diagnostic-cloud/reference-guide/identifying-top-performance-issues-in-your-system-with-pega-predictive-diagnostic-cloud.html) [Using real-time container APIs](https://docs-previous.pega.com/pega-customer-decision-hub-user-guide/85/using-real-time-container-apis) [Triggering a real-time container with the Container REST service](https://docs-previous.pega.com/pega-customer-decision-hub-user-guide/85/triggering-real-time-container-container-rest-service) The error indicates an issue with PegaMKTContainer|V3 - this is not a problem with PDC but with Marketing and configuration causing pderformance issues. Have you made changes to the application stack or to “simulation/enableSampling” DSS? Can you check PDC alerts for any Strategy emitting empty payloads where fields contain blanks for customized outcome type . I suggest that you go through the PDC landing pages and full logs to identify the Marketing processes that are causing problems. Please log a [support incident](http://msp.pega.com/) if you require further help with this. Can you provide the INC reference here so that we can help track it? ---
**Author:** ![prasadn1](https://avatars.discourse-cdn.com/v4/letter/p/90db22/32.png) [@prasadn1](https://forums.pega.com/u/prasadn1)\ **Post date:** [March 27, 2023, 9:16am UTC](https://forums.pega.com/t/pega0011-alerts-in-production/4221/3 "2023-03-27T09:16:04Z")
@MarijeSchillern Hi Marije. Thanks for the reply. From logs i can see PEGA0020 is coming along with PEGA0011. When i checked in logs i can see one of the connect rest api is taking more time to get response. Kindly please let me know how to handle this. ---
**Author:** ![MarijeSchillern](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marijeschillern/32/23321_2.png) [@MarijeSchillern](https://forums.pega.com/u/MarijeSchillern)\ **Post date:** [March 27, 2023, 9:33am UTC](https://forums.pega.com/t/pega0011-alerts-in-production/4221/4 "2023-03-27T09:33:40Z")
@prasadn1 there are lots of posts on the forum for ‘slow response connect rest’ issues: > **[Connect REST taking more time | Support Center](https://support.pega.com/question/connect-rest-taking-more-time)** > > Hi, Our application is using Connect REST to connect an external system. Though the service is returning the response when it receives the request in milli seconds, Pega is taking more time to hit the service layer. When I run tracer, I can see the... > **[How to investigate performance issue on Connector's pxConnectInMapReqElapsed...](https://support.pega.com/question/how-investigate-performance-issue-connectors-pxconnectinmapreqelapsed)** > > Hi,   I got issue Connector work slow but I see pxConnectInMapReqElapsed was slow more than 10 seconds. How to debug or tracer on that process. Is it OOTB's or My customization rules.   Thank you. \*\*\*Edited by Moderator: Pallavi to update platform... > **[Connect REST Response mapping issue | Support Center](https://support.pega.com/question/connect-rest-response-mapping-issue)** > > While running the rest connector we are getting "com.pega.pegarules.pub.services.InboundMappingException: Exception occurred while mapping incoming response to .response\_POST " exception for the same connector earlier there was no issue and some... Improve the performance of activity-based REST services by filtering the request and response . Have you tested the Rest Service with post man/Rest client? please enable logger for Connect-REST . The issue could be due to various reasons: 1# Your mapping many attributes to your Request as well as Response for this connector 2# You might have a slow responding Database at the backend. Pega005 and 42 will give an idea. Please trace it and check where the time is actually spent. Our main documentation also gives you steps to troubleshoot: > **[Pegasystems Documentation](https://docs.pega.com/bundle/alerts/page/platform/alerts/intg0001-rest-connector-timeout.html)** [Pegasystems Documentation](https://docs-previous.pega.com/whats-new-pega-platform/improve-performance-activity-based-rest-services-filtering-request-and-response-86)? > **[Pegasystems Documentation](https://docs.pega.com/bundle/alerts/page/platform/alerts/pega0020-alert-total-connect-interaction-time-exceeds-limit.html)** → please go through them and try out the suggestions. If you need further help and if no other forum users provide any further input or suggestions then you can log a support ticket via on the [MSP](http://msp.pega.com/). Please provide the INC ticket number here if you decide to go down that route so that we can help track it. You wll be asked for the troubleshooting you have carried out.