• Documentation
  • Back to www.mscrm-addons.com
  • Documentation
  • Back to www.mscrm-addons.com
home/Knowledge Base/DocumentsCorePack(DCP)/Heartbeat service restart behaviour

Heartbeat service restart behaviour

37 views 0 Updated on March 30, 2020

This blog article outlines how the heartbeat service restart behaviour works in case that Dynamics 365 is not available for some reason. For example, there is an update: after the update Dynamics 365 will work as usual, but not our services – they will stop. Therefore we provide the heartbeat service.

The heartbeat service is verifying every service available in the WatchedConfigurations registry key. It runs every 5 minutes and verifies each service is in “Running” state.

Not running services are checked for 20 times every  5 minutes. If the service has still not been restarted after those 100 minutes, the heartbeat service will check and try to restart this service every 50 minutes for a total of 24 hours monitoring time of a particular service.

If a service still has failed to start after those 24 hours, the heartbeat service will stop trying to restart this service.

Any service with the “AlwaysRestartService“ flag set will never be removed from the watched configurations, regardless of its state.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Was this helpful?

Yes  No
Related Articles
  • How to access mscrm-addons product settings in Dynamics 365
  • One-Click-Actions (OCAs) in DocumentsCorePack
  • Service Configuration options
  • Multipart documents in DocumentsCorePack
  • Azure Active Directory Licensing counts explained
  • DocumentsCorePack: Performance benchmark, limitations & scalability
Latest Articles
  • How to display various activity-attributes within multiple rows in Gantt view
  • Recap: European Power Platform Conference 2022
  • How to solve the issue with DocumentsCorePack fields in Arabic text
  • How to access mscrm-addons product settings in Dynamics 365
  • One-Click-Actions (OCAs) in DocumentsCorePack
Popular Articles
  • DocumentsCorePack Online Service Configuration
  • Where do I find the Unique Organization name in Microsoft Dynamics 365?
  • mscrm-addons.com Application Access for Dynamics 365 (App Access) – DocumentsCorePack
  • How to activate the DocumentsCorePack connector for PowerApps & Microsoft Flow
  • How licenses are counted
Top Rated Articles
  • IMPORTANT information for Dynamics 365 online customers using DocumentsCorePack and/or AttachmentExtractor
  • How to activate the DocumentsCorePack connector for PowerApps & Microsoft Flow
  • Step-by-Step: How to configure a One-Click-Action
  • Can you save data capacity by moving email content?
  • Online Services: Required Application Permissions
Categories
  • *News and General Infos* 50
  • Template Designer(DCP 160
  • DocumentsCorePack(DCP 180
  • TelephoneIntegration (TI 64
  • AttachmentExtractor (AE 55
  • PowerSearch (PS 43
  • ActivityTools (AT 57
  • SmartBar (SB 51
  • GroupCalendar (GC 45
Our Vision

“We see it as our purpose to provide products that simplify and speed up our customers’ Microsoft Dynamics 365 experience.”

Knowledgebase
LogIn
mscrm-addons.com
  • Products
  • Online Shop
  • Downloads
  • My Account
About Us
  • About Us
  • Case Studies
  • Newsletter
  • Partner Program
  • Contact
Support
  • Support
  • Terms & Conditions
  • Documentation
  • Webinars
  • Legal Documents
  • Impressum
  • © 2022 www.mscrm-addons.com. All Rights Reserved.