Demandbase sends system notifications when issues affect integrations, data synchronization, write-back operations, audiences, or automations.
Each notification has a severity level of High, Medium, or Low to help you assess its impact and determine whether action is required.
Important:
- System Notifications only shows notifications your account has received. You may not see every notification type listed in this article.
- Some notification types have different severity levels depending on the issue.
- Notification reasons may include error messages returned by connected platforms. Actual messages may differ from the examples in this article.
To configure system notification delivery, see Configure System Notifications.
Access System Notifications
You can view, filter, customize, and export system notifications for your account.
- From the left navigation bar, go to
Settings > System Monitoring > System Notifications.
- Use the following options to review notifications:
- Filter notifications: Filter by Platform, Severity, Status, or Object.
- Edit Columns: Select which columns to display in the table.
- Export: Export the notification report.
Important: Changes to system notifications affect all recipients configured to receive notifications. See Configure System Notifications.
Understanding System Notification Severity Levels
Demandbase assigns a severity level to each system notification based on the type of issue and its impact.
| Severity | Description |
| High | A critical issue prevents an integration, sync, audience, or automation from working correctly and requires action. |
| Medium | An issue affects specific functionality or configuration but may not interrupt the entire integration or process. |
| Low | An informational, temporary, or record-level issue that typically does not interrupt the overall process. |
Understanding System Notification Details
Each system notification includes details to help you identify the issue, assess its impact, and determine the appropriate action.
| Field | Description |
| Platform | The connected platform associated with the notification, such as Salesforce, Marketo, or LinkedIn. Demandbase appears for platform-related issues. |
| Object | The object associated with the notification, when applicable. |
| Type | The issue category, such as Credentials / Expired, Writeback, or Orchestration. |
| Reason | The specific error or condition that triggered the notification. |
| Severity | High, Medium, or Low. |
| Occurrence | The number of times the same notification occurred. Notifications with matching Platform, Type, and Reason values are grouped together. |
| Impact | The number of affected audiences or automations, when applicable. |
Important:
- Some types use system-generated labels, such as Uncategorized, Run Job, or Demandbase Permission. Check the Reason field for details.
- The Platform field may display an internal integration identifier, such as
IH_d10003_i10004for Gong or an identifier beginning withLR_for LiveRamp. - If a resolved issue occurs again, the notification reopens with the severity of the latest occurrence.
High Severity System Notifications
High severity notifications indicate issues that require action to restore affected functionality.
Integration Credentials and Connection Error Examples
These notifications indicate that an integration has expired credentials, cannot authenticate, or lacks the required permissions.
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Salesforce, Pardot, HubSpot, Marketo, Eloqua, Act-On, Outreach, Salesloft, LinkedIn, AdRoll/RollWorks, Terminus, Slack | Credentials / Expired | Credentials need to be updated. | Go to Settings > Integrations and reconnect the integration. |
| Credentials / Expired | Refresh token expiration. | Re-authenticate LinkedIn before the token expires. Notifications are sent 30, 21, 14, and 1 day before expiration and after expiration. | |
| Gong | Credentials / Expired | Update Gong on Integrations Page. | Reconnect Gong in Settings > Integrations. |
| Salesforce | Credentials / Expired | Session expired or invalid. | Reconnect Salesforce in Settings > Integrations. |
| Salesforce (JWT) | Credentials / Expired | Salesforce JWT token expired on date. | Re-authenticate Salesforce. This notification is Medium before expiration and High afterward. |
| Salesforce | Credentials / Expired | Salesforce sync authentication failures. | Reconnect Salesforce. Continued failures automatically disable the integration. |
| Salesforce | Credentials / Expired | Salesforce integration has been disabled. | Reconnect Salesforce and verify that synchronization resumes. |
| Pardot | Credentials / Expired | Pardot Business Unit ID is inactive or not found. | Verify the Business Unit ID with your Salesforce admin and update the integration. |
| Microsoft Dynamics | Credentials / Expired | Dynamics credentials need to be updated. | Reconnect Microsoft Dynamics. |
| Microsoft Dynamics | Demandbase Permission | Dynamics API missing permissions, unavailable, or returned an exception. | Ask your Dynamics admin to grant the required permissions and verify API availability. |
| Salesforce Marketing Cloud | Credentials / Expired | SFMC Credentials Expired. | Reconnect Salesforce Marketing Cloud. |
| Salesforce Marketing Cloud | Access Denied | Access denied to a Data Extension or folder. | Grant the installed package access to the affected Data Extensions. |
| Salesforce Marketing Cloud | Object not found | Data Extension not found. | Verify that the Data Extension exists or update the integration. |
| Salesforce Marketing Cloud | Schema changed | SFMC Data Extension Schema Mismatch. | Restore the expected fields or update the field mapping. |
| Salesforce Marketing Cloud | Provider API Exception | Marketing Cloud API error. | Contact Demandbase Support if the issue persists. |
| Salesforce | Provider API Exception | Salesforce API error during synchronization. | Verify that the sync user is active and has API access. Contact Support if the issue persists. |
| Pardot, Eloqua | Demandbase Permission | Insufficient permissions or unauthorized access. | Grant the integration user the required permissions. |
| Pardot | Demandbase Permission | Pardot business unit not configured or Salesforce integration missing. | Connect Salesforce and configure the Pardot Business Unit ID. |
| HubSpot | Uncategorized | Unknown HubSpot failure or API error. | Reconnect HubSpot and verify the required permissions. |
| Eloqua | Uncategorized | Authentication or synchronization error. | Reconnect Eloqua. Contact Support if the issue persists. |
| Uncategorized | LinkedIn server internal error. | Contact Support if the issue persists. | |
| Salesforce | Uncategorized | Account reconciliation or authentication failure. | Reconnect Salesforce. Contact Support if the issue persists. |
| Salesforce and other CRMs | CRM Reconcile Job Failure | Failed to reconcile CRM records. | Contact Demandbase Support. |
API Limit Error Examples
These notifications indicate that an integration has reached its configured API quota.
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Marketo | API Limit | Exceeded Marketo API quota of N. | Sync pauses until the quota resets. Increase the limit on the Data Sync page if your Marketo subscription allows it. |
Audience and Destination Error Examples
These notifications indicate that an audience destination is unavailable, inaccessible, or incorrectly configured.
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Object not found | LinkedIn matched audience deleted externally. | Remove the destination or create a new LinkedIn audience destination. | |
| LinkedIn and other audience destinations | Object not found | Ad account API returned a 404 error. | Verify that the ad account exists and is accessible. Update the audience destination. |
| LiveRamp | Object not found | Connection is removed. | Reconnect LiveRamp or remove the audience destination. |
| LinkedIn, HubSpot, and other audience destinations | Provider API Exception | Audience sync failed because an authenticated member was not found. | Reconnect using an account with the required access. Contact Support if the issue persists. |
Automation and Data Integrity Error Examples
These notifications indicate that an automation or Data Integrity process cannot complete successfully.
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Demandbase | Orchestration | Automation or Audience name failed. Automation is disabled. | Fix the error and re-enable the automation. |
| Demandbase | Orchestration | Job ID not started, stuck, or incomplete. | Review the automation run history. Contact Support if the issue persists. |
| Salesforce, HubSpot, Microsoft Dynamics, Marketo, Outreach, Salesloft | Uncategorized | API error during an automation step. | Check the integration in Settings > Integrations. Contact Support if the issue persists. |
| Demandbase | Data Integrity | CRM error during a Data Integrity automation. | Review the error details and correct the affected CRM records. |
Data and Field Error Examples
These notifications indicate that a configuration references a field that is no longer available.
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Demandbase | Field not found | Audience name contains an invalid filter. | Edit the audience and replace or remove the unavailable field. |
Medium Severity System Notifications
Medium severity notifications indicate issues that affect specific functionality or require configuration changes but may not interrupt the entire integration or process.
Error Examples
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Salesforce (JWT) | Credentials / Expired | Salesforce JWT token expires on date. | Re-authenticate Salesforce before expiration. The notification becomes High after expiration. |
| Demandbase | Email Authentication | User email authentication failed. | Ask the user to reconnect their email or calendar account. |
| Demandbase, LinkedIn | Access Denied | User access denied or ad account creator access removed. | Restore access or reconnect with an authorized account. |
| Salesforce | Report | Unable to read a specific Salesforce report because of expired credentials, missing access, unavailable objects, or API limits. | If you build Account Lists from Salesforce Reports, ask your Salesforce admin to verify access to the affected reports. |
| Salesforce | Writeback | Missing or inactive Demandbase package fields. | Install the latest Demandbase AppExchange package and grant access to the required fields. |
| Salesforce | Writeback | Incorrect Installation. | Repair or reinstall the Demandbase AppExchange package. |
| Salesforce | Writeback | Lead/Contact write backs are not allowed. | Contact your CSM to enable Lead and Contact write-back if needed. |
| Salesforce and other CRMs | Writeback | Lead-to-account write-back blocked by connected app permissions. | Ask your CRM admin to allow the Demandbase connected app. |
| Demandbase | Data Import | S3 import processing or activity type validation error. | Check the import file format and folder structure. |
| Demandbase | Field not found | Account or Person filter references an unavailable field. | Edit the filter and replace the field. |
| Intent provider connections | Credentials / Expired | Intent provider credentials need to be updated. | Update the credentials in Settings > Integrations. |
| Demandbase | Orchestration | Automation automatically deactivated after an extended period without runs. | Reactivate the automation if needed. |
| Salesforce, Microsoft Dynamics, HubSpot | Uncategorized | Automation cannot update a missing, invalid, or unavailable field value. | Verify the field and edit permissions, then run the sync again. |
| Salesforce, Microsoft Dynamics | Run Job | Invalid object type for an automation step. | Update the automation to use a supported object. |
| Salesforce, Outreach | Orchestration | Account or person not found. | Verify that the record exists in the destination platform. Contact Support if the issue persists. |
| Demandbase | Demandbase Permission | Unable to add member to list. | Try again. Contact Support if the issue persists. |
Low Severity System Notifications
Low severity notifications typically indicate record-level errors, informational events, or temporary conditions that do not interrupt the overall process.
Error Examples
Platform |
Type |
Example Reason |
Recommended Action |
|---|---|---|---|
| Salesforce | Writeback | REQUIRED_FIELD_MISSING, FIELD_CUSTOM_VALIDATION_EXCEPTION, INACTIVE_OWNER_OR_USER, NUMBER_OUTSIDE_VALID_RANGE, or APEX_FAILED. | Correct the affected record or ask your Salesforce admin to review validation rules or triggers. |
| Salesforce | Writeback | INVALID_FIELD_FOR_INSERT_UPDATE on a Demandbase package field (engagio__…). |
Install the latest AppExchange package and grant edit access to the required fields. |
| Salesforce, HubSpot, other CRMs | Writeback | Field value exceeds the allowed length or HubSpot write-back error. | Shorten the value or increase the destination field length if supported. |
| Microsoft Dynamics | Field sync / Writeback | Entity sync or write-back failed. | Review the affected records. |
| HubSpot | API Limit | Exceeded HubSpot DAILY API rate limit. | No action required. The limit resets at midnight in your HubSpot time zone. |
| Salesforce | Provider API Exception | Salesforce requested that the job run again later. | No action required. The job retries automatically. |
| Pardot | Provider API Exception | Failed to parse Pardot API response. | Contact Support if the issue persists. |
| Salesforce | Report | Salesforce report sync or new reports sync failed. | Review if you use Salesforce Reports to build Account Lists. |
| Marketo | Field not found | Error, Field not found. | Verify that the mapped Marketo field exists. |
| Demandbase | List Membership Refresh Failure | Failed to refresh List: list name. | Review the list filters. Contact Support if the issue persists. |
| Marketo, Salesloft, Outreach, Salesforce | Orchestration | Person, campaign, email address, or assignee not found; unable to add or create a person; mailbox error. | Review the affected records and automation settings. |
| Salesloft | Uncategorized | Unable to add to cadence or cadence already in progress. | Review the affected person. No action is needed if the person is already in the cadence. |
| Outreach | Uncategorized | Authentication error during an automation step. | Retry the action. Reconnect Outreach if the issue persists. |
| Demandbase | Orchestration / Uncategorized | Invalid list, list type, or member type. | Update the automation to use a valid list or member type. |
| Demandbase | Demandbase Permission | User is not an admin. | Ask an admin to run or update the automation. |