Messages that can appear in a Dialer Health view

Status Messages

History Messages

The calculated calls per connect value for a campaign is greater than the configured maximum calls per agent.

Configured line group is invalid or contains no lines.

Campaign has fewer than six active agents, potentially decreasing agent utilization and increasing abandon rate.

Current abandonment rate exceeds the configured target rate.

Contact cache has been depleted.

Configured Zone Set is blocked all callable contacts.

Dialing is being restricted because the configured line capacity has been reached.

History updates (campaign stats, agent stats, call history) are accumulating in queue.

Contact list updates are accumulating in queue.

Current abandonment rate exceeds the configured strict abandonment rate.

Dialer Transaction Server is not responding.

No callable contacts left.

History updates (campaign stats, agent stats, call history) are accumulating in queue.

Contact list updates are accumulating in queue.

The database provider in use is not recommended for use with Dialer.

Default database is not specified or UDL file is not compatible with Dialer.

Default database is not specified or the UDL file is invalid.

Campaign is paused because TS API calls are failing, likely due to TS Server not running.

DNC scrubbing failed.

Policy set contains one or more behaviors referencing contact columns not used by the campaign.

Agent has none of the required skills for the campaign, so no calls will be placed for the agent.

Automatic time zone mapping is unavailable because the time zone source data could not be initialized.

Automatic time zone mapping source data file is not accessible because no CCS dial plan is available for phone number standardization.

Automatic time zone mapping source data file is not accessible because the map data set file is missing.

Automatic time zone mapping is unavailable for all campaigns because no automatic time zone mappings are present.

Automatic time zone mapping is unavailable because no time zone map data sets are configured for automatic time zone mapping.

An agent has been placed on break because a TS API call failed.

A campaign is reserving a high percentage of active agents for non-Dialer calls.

A campaign is recycling its contact list.

An agent logged into a campaign with a persistent connection, but no persistent connection wav file is configured.

Dialing is being restricted by the configured maximum call rate setting.

A problem occurred while attempting to load the configuration XML file.

Campaign could not be found in the dialer cache.

Failure to register Dialer site with central campaign server.

A memory allocation failed while trying to create a new object.

Agent automatically logged out because the connection between the agent's scripter application and Dialer was lost.

Configured line group is not active on the server.

Call ID attribute not present among contact attributes.

Campaign ID not found among contact attributes.

An unknown exception occurred.

A Win32 exception occurred.

Dialer Transaction Server failed to start.

Dialer Transaction Server is restarting because of too many hung threads.

A COM exception occurred.

An exception occurred.

A Notifier request failed.

Insert or update operation was aborted because there was no data to process.

Data passed in as a date value could not be parsed.

Warnings were generated while processing a database update.

The ACD workgroup is not active on the server.

An error occurred while validating a database table.

A policy set could not be loaded by the campaign server.

A query for the number of remaining contacts failed.

A policy reported an error.

A connection to the database could not be established.

A SQL operation failed to complete.

A behavior failed to run properly.

An event interface object was not found in the global interface table.

An error occurred while attempting to evaluate a rule item

The campaign server was unable to read/write the xml configuration file.

The campaign server management interface pointer could not be obtained

An operation failed because the requested object identifier was not found

The campaign server's request for statistical data failed

The campaign server was unable to commit table properties to the configuration file.

The campaign server has reached the maximum number of threads allowed, typically because all processing threads are hung.

Unable to retrieve the number of contacts left in the current recycle.

An error was reported by a rule action.

An error occurred while trying to load a property.

An error occurred while looking up the active station for an agent.

Campaign initialization failed while processing related properties.

A database table could not be initialized or validated.

An error status message was deactivated.

A contact list updated was in an incorrect format.

A campaign was paused because it exceeded the maximum number of errors.

A campaign was paused because it could not load the contact columns.

An error occurred while attempting to enable workgroup period stats.

A requested action was ignored because the associated agent is not logged into the campaign.

A requested action was ignored because the associated agent is not active in the campaign.

A campaign has been manually paused.

An interaction could not be found in the dialer cache.

The scheduled date passed in from the script was invalid.

A call was placed and routed to an agent, but not completed.

The campaign will not be started because it is not configured as active.

A contact does not have a callable phone number.

No lines available in the line group.

All campaigns are paused until CPU utilization drops below the configured point.

An agent could not be found in the dialer cache.

A campaign has stopped because it has completed the maximum number of recycles.

A campaign has entered forced power dialing mode because its abandon rate exceeded the maximum rate.

Predictions made for a campaign are paused because the number of inbound calls is greater than the configured maximum for the workgroup.

A policy reported a warning.

A rule action reported a warning.

A reset or recycle operation for a campaign was ignored because the campaign has already completed.

An agent attempted to disposition an interaction that he/she does not own.

A campaign's pace was manually adjusted.

An agent changed to an available status prior to call disposition.

A warning status message was deactivated.

A campaign has started.

Dialer Transaction Server has started.

A campaign has been manually un-paused.

All campaign dialing has resumed because CPU utilization dropped below the configured maximum.

A campaign has stopped.

A contact list has recycled.

A campaign has exited forced power mode due to the abandon rate dropping below the configured maximum.

A campaign has resumed making predictions due to the number of inbound calls dropping below the configured maximum for the workgroup.

A campaign has been manually restarted.

A policy reported an informational message.

A rule action reported an informational message.

One or more database tables were created for a campaign.

A campaign was restarted by a rule.

A campaign was restarted by a user.

A campaign was recycled by a rule.

A campaign was recycled by a user.

A campaign has stopped because it reached the maximum recycle count due to zone blocking.

An informational status message was deactivated.