Delivery performance and troubleshooting delivery-performance-troubleshooting

For comprehensive best practices on delivery performance, platform optimization, quarantine management, database maintenance, and scheduling recommendations, refer to the Campaign v8 Delivery best practices documentation.

Performance optimization performance-optimization

For Campaign Classic v7 hybrid/on-premise deployments, the following database and infrastructure optimizations can improve delivery performance.

Database optimization

Index addresses to optimize the performance of SQL queries used in the application. An index can be declared from the main element of the data schema. This optimization requires direct database access and schema customization available in on-premise deployments.

Infrastructure tuning

Large deliveries configuration: Deliveries to over one million recipients need space in the sending queues. For on-premise installations, MTA children can be configured to handle custom batch sizes. Contact your system administrator to adjust these settings based on your infrastructure capacity.

Database maintenance database-maintenance

For Campaign Classic v7 hybrid/on-premise deployments, platform and database maintenance directly affects delivery sending performance.

Regular maintenance tasks include:

Database cleanup: Use the database cleanup workflow to remove old delivery logs, tracking data, and temporary tables. Poor database maintenance can slow down delivery preparation and sending.

Database performance monitoring: Monitor query performance, index fragmentation, and table statistics. For detailed guidance, refer to this page.

Technical workflow monitoring: Ensure all technical workflows (especially cleanup, tracking, and deliverability update workflows) are running correctly without errors.

Troubleshooting delivery issues troubleshooting

For Campaign Classic v7 hybrid/on-premise deployments, the following troubleshooting steps are specific to infrastructure you manage.

MX rules configuration

If you experience throttling issues with specific ISPs, you may need to review and adjust your MX rules configuration. For more information about MX rules and quotas, refer to this section.

Database maintenance for delivery performance

If you encounter the following error in mid-sourcing deployments:

Error during the call of method 'AppendDeliveryPart' on the mid sourcing server: 'Communication error with the server: please check this one is correctly configured. Code HTTP 408 'Service temporarily unavailable'.

The cause is linked to performance issues where the marketing instance spends too much time building data before sending it to the mid-sourcing server.

For on-premise installations, perform a vacuum and reindex on the database. For more information on database maintenance, refer to this section.

You should also restart all workflows with a scheduled activity, and all workflows in failed status. Refer to this section.

Technical workflow monitoring

For on-premise installations, ensure that all technical workflows related to deliverability are running without errors:

Deliverability update workflow: Updates bounce mail qualification rules and deliverability indicators.

Tracking workflow: Processes tracking data for sent deliveries.

Database cleanup workflow: Regularly purges old delivery logs and temporary tables to maintain performance.

Check workflow status in Administration > Production > Technical workflows.

Related topics