From 62ad3bee00522cfca88d83e4c52fe58c48b4a0bb Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Tue, 3 Feb 2026 11:32:03 +0100 Subject: [PATCH 01/12] messenger support in CDP described --- docs/cdp/cdp_data_export_schedule.md | 45 +++++++++++++++++++++++++++- 1 file changed, 44 insertions(+), 1 deletion(-) diff --git a/docs/cdp/cdp_data_export_schedule.md b/docs/cdp/cdp_data_export_schedule.md index 7102d57bc7..2921c86ac3 100644 --- a/docs/cdp/cdp_data_export_schedule.md +++ b/docs/cdp/cdp_data_export_schedule.md @@ -65,4 +65,47 @@ php bin/console ibexa:cdp:stream-product-data --help ```bash php bin/console ibexa:cdp:stream-content-data --help -``` \ No newline at end of file +``` + +## [[= product_name_base =]] Messenger support for large batches of data + +CDP uses [[= product_name_base =]] Messenger to process data. +This approach improves performance and reliability when processing large amounts of CDP user records. +For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). + +By using Messenger while working with large batches of data, requests are queued instead of being processed synchronously: + +- queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) +- every single data is recorded in the database +- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger](https://symfony.com/doc/current/messenger.html) configuration +- processing happens at set intervals to avoid timeouts and keep the system stable + +Messenger requires a dedicated database table. +This table is not created automatically and must be added manually using a database update script. + +Follow the [database update procedure](https://doc.ibexa.co/en/latest/update_and_migration/from_5.0/update_from_5.0/#database-update) to proceed. + +1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. + +2\. Add `bulk_async_threshold` setting in the `config/packages/ibexa_cdp.yaml` configuration: + +``` bash +ibexa_cdp: + bulk_async_threshold: 100 # Default: 100 items +``` + +Available options: + +- `bulk_async_threshold` (integer, default: 100) - minimum number of items required to trigger asynchronous processing + - below threshold - items are processed immediately in a single request, using the standard synchronous behavior + - at/above threshold - items are automatically dispatched to the asynchronous queue for background processing + +3\. Make sure that the [worker starts](background_tasks.md#start-worker) together with the application to watch the transport bus: + +``` bash +php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenger.bus +``` + +!!! note "Deploying Symfony Messenger" + + For more information about deploying the Messenger to production, see [Symfony documentation]([[= symfony_doc =]]/messenger.html#deploying-to-production). From 46eaacb700ca0ab19079ae54016742fff0b4bd6e Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 4 Feb 2026 14:00:32 +0100 Subject: [PATCH 02/12] name fixes after review --- docs/cdp/cdp_activation/cdp_data_export.md | 39 ++++++++++++++++++++ docs/cdp/cdp_data_export_schedule.md | 43 ---------------------- 2 files changed, 39 insertions(+), 43 deletions(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index cbc932559d..9dd371b828 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -133,3 +133,42 @@ Finally, you can specify the audiences you wish to include. !!! note "CDP requests" All CDP requests are logged in with `debug` severity. + +### [[= product_name_base =]] Messenger support for large batches of data + +CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](www.raptorservices.com/). +This approach improves performance and reliability when processing large amounts of CDP user records. +For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). + +By using Messenger while working with large batches of data, requests are queued instead of being processed synchronously: + +- queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) +- every single data is recorded in the database +- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger](https://symfony.com/doc/current/messenger.html) configuration +- processing happens at set intervals to avoid timeouts and keep the system stable + +Follow the [database update procedure](https://doc.ibexa.co/en/latest/update_and_migration/from_5.0/update_from_5.0/#database-update) to proceed. + +1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. + +2\. Add `bulk_async_threshold` setting in the `config/packages/ibexa_cdp.yaml` configuration: + +``` bash +ibexa_cdp: + bulk_async_threshold: 100 # Default: 100 items +``` + +Available options: + +- `bulk_async_threshold` (integer, default: 100) - minimum number of items required to trigger asynchronous processing + - below threshold - items are processed immediately in a single request, using the standard synchronous behavior + - at/above threshold - items are automatically dispatched to the asynchronous queue for background processing + +3\. Make sure that the [worker starts](background_tasks.md#start-worker) together with the application to watch the transport bus: + +``` bash +php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenger.bus +``` + +For more information, see [Start background task worker](background_tasks.md#start-worker). + diff --git a/docs/cdp/cdp_data_export_schedule.md b/docs/cdp/cdp_data_export_schedule.md index 2921c86ac3..49c94078e5 100644 --- a/docs/cdp/cdp_data_export_schedule.md +++ b/docs/cdp/cdp_data_export_schedule.md @@ -66,46 +66,3 @@ php bin/console ibexa:cdp:stream-product-data --help ```bash php bin/console ibexa:cdp:stream-content-data --help ``` - -## [[= product_name_base =]] Messenger support for large batches of data - -CDP uses [[= product_name_base =]] Messenger to process data. -This approach improves performance and reliability when processing large amounts of CDP user records. -For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). - -By using Messenger while working with large batches of data, requests are queued instead of being processed synchronously: - -- queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) -- every single data is recorded in the database -- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger](https://symfony.com/doc/current/messenger.html) configuration -- processing happens at set intervals to avoid timeouts and keep the system stable - -Messenger requires a dedicated database table. -This table is not created automatically and must be added manually using a database update script. - -Follow the [database update procedure](https://doc.ibexa.co/en/latest/update_and_migration/from_5.0/update_from_5.0/#database-update) to proceed. - -1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. - -2\. Add `bulk_async_threshold` setting in the `config/packages/ibexa_cdp.yaml` configuration: - -``` bash -ibexa_cdp: - bulk_async_threshold: 100 # Default: 100 items -``` - -Available options: - -- `bulk_async_threshold` (integer, default: 100) - minimum number of items required to trigger asynchronous processing - - below threshold - items are processed immediately in a single request, using the standard synchronous behavior - - at/above threshold - items are automatically dispatched to the asynchronous queue for background processing - -3\. Make sure that the [worker starts](background_tasks.md#start-worker) together with the application to watch the transport bus: - -``` bash -php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenger.bus -``` - -!!! note "Deploying Symfony Messenger" - - For more information about deploying the Messenger to production, see [Symfony documentation]([[= symfony_doc =]]/messenger.html#deploying-to-production). From 579be5332f576b226d00b4d8a61d107d5e119535 Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 4 Feb 2026 14:12:40 +0100 Subject: [PATCH 03/12] reorder, update doc added --- docs/update_and_migration/from_4.6/update_from_4.6.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/update_and_migration/from_4.6/update_from_4.6.md b/docs/update_and_migration/from_4.6/update_from_4.6.md index 6f33fe174b..b283ed4a9b 100644 --- a/docs/update_and_migration/from_4.6/update_from_4.6.md +++ b/docs/update_and_migration/from_4.6/update_from_4.6.md @@ -572,6 +572,11 @@ composer require guzzlehttp/guzzle:^6.5 php-http/guzzle6-adapter:^2.0 With the product updated to the latest version, you can now finish the update process or proceed to updating the LTS Updates packages. +### Messenger support in CDP + +If you are using CDP and have not configured Ibexa Messenger yet, do so now. +Follow the [Messenger setup instructions](https://doc.ibexa.co/en/4.6/infrastructure_and_maintenance/background_tasks/#install-package) to continue. + ## LTS Updates [LTS Updates](https://doc.ibexa.co/en/4.6/ibexa_products/editions/#lts-updates) are standalone packages with their own update procedures. From 07c5a292332ecac9b6e43f861079e8a54d616eeb Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 4 Feb 2026 14:25:06 +0100 Subject: [PATCH 04/12] https fix --- docs/cdp/cdp_activation/cdp_data_export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 9dd371b828..25cb65078d 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -136,7 +136,7 @@ Finally, you can specify the audiences you wish to include. ### [[= product_name_base =]] Messenger support for large batches of data -CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](www.raptorservices.com/). +CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](https://www.raptorservices.com/). This approach improves performance and reliability when processing large amounts of CDP user records. For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). From 6b3f511fb93252652089cc37c2dd6aa2195f07fd Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 4 Feb 2026 16:13:55 +0100 Subject: [PATCH 05/12] conflict resolved --- docs/cdp/cdp_activation/cdp_data_export.md | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 25cb65078d..de2d6c020f 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -172,3 +172,32 @@ php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenge For more information, see [Start background task worker](background_tasks.md#start-worker). +### CDP Monolog channel + +CDP Monolog channel handles webhook logs for easier separation of logs. + +```bash +- { name: monolog.logger, channel: ibexa.cdp.webhook } +``` + +It's possible to configure `ibexa.cdp.webhook` Monolog channel to direct all logs to specific stream, file, or service. +This allows webhook logs to be stored separately from the main application logs for easier debugging and analysis. + +To do it, in `config/packages/monolog.yaml` file, define a new handler for the `ibexa.cdp.webhook` channel that directs CPD Webhook events to a separate file. +It can be configured in both `dev` and `prod` environments, for example: + +```yaml +monolog: + handlers: + cdp_webhook: + type: stream + path: "%kernel.logs_dir%/cdp_webhook_%kernel.environment%.log" + level: debug + channels: [ 'ibexa.cdp.webhook' ] +``` + +If you want to avoid redundant or duplicate entries in the other logs, exclude the webhook channel by: + +```yaml +channels: ["!ibexa.cdp.webhook"] +``` From 6af0436a3c51161326314aeec2e555a8175f339b Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 4 Feb 2026 16:08:29 +0100 Subject: [PATCH 06/12] conflict resolved --- docs/cdp/cdp_activation/cdp_data_export.md | 37 ++++++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index de2d6c020f..03526b2c79 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -201,3 +201,40 @@ If you want to avoid redundant or duplicate entries in the other logs, exclude t ```yaml channels: ["!ibexa.cdp.webhook"] ``` +### [[= product_name_base =]] Messenger support for large batches of data + +CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](www.raptorservices.com/). +This approach improves performance and reliability when processing large amounts of CDP user records. +For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). + +By using Messenger while working with large batches of data, requests are queued instead of being processed synchronously: + +- queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) +- every single data is recorded in the database +- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger](https://symfony.com/doc/current/messenger.html) configuration +- processing happens at set intervals to avoid timeouts and keep the system stable + +Follow the [database update procedure](https://doc.ibexa.co/en/latest/update_and_migration/from_5.0/update_from_5.0/#database-update) to proceed. + +1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. + +2\. Add `bulk_async_threshold` setting in the `config/packages/ibexa_cdp.yaml` configuration: + +``` bash +ibexa_cdp: + bulk_async_threshold: 100 # Default: 100 items +``` + +Available options: + +- `bulk_async_threshold` (integer, default: 100) - minimum number of items required to trigger asynchronous processing + - below threshold - items are processed immediately in a single request, using the standard synchronous behavior + - at/above threshold - items are automatically dispatched to the asynchronous queue for background processing + +3\. Make sure that the [worker starts](background_tasks.md#start-worker) together with the application to watch the transport bus: + +``` bash +php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenger.bus +``` + +For more information, see [Start background task worker](background_tasks.md#start-worker). From ddcf2971a6888240d0cdbabf9f62b95f974844cc Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Wed, 4 Feb 2026 14:25:06 +0100 Subject: [PATCH 07/12] https fix --- docs/cdp/cdp_activation/cdp_data_export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 03526b2c79..241c75d58e 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -203,7 +203,7 @@ channels: ["!ibexa.cdp.webhook"] ``` ### [[= product_name_base =]] Messenger support for large batches of data -CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](www.raptorservices.com/). +CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](https://www.raptorservices.com/). This approach improves performance and reliability when processing large amounts of CDP user records. For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). From f08110f723ebf0115c9ea74064362a6c15fbf250 Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Thu, 5 Feb 2026 10:20:21 +0100 Subject: [PATCH 08/12] fix after rev --- docs/cdp/cdp_activation/cdp_data_export.md | 37 ------------------- .../from_4.6/update_from_4.6.md | 10 ++--- 2 files changed, 5 insertions(+), 42 deletions(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 241c75d58e..de2d6c020f 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -201,40 +201,3 @@ If you want to avoid redundant or duplicate entries in the other logs, exclude t ```yaml channels: ["!ibexa.cdp.webhook"] ``` -### [[= product_name_base =]] Messenger support for large batches of data - -CDP uses [[= product_name_base =]] Messenger to process incoming data from [Raptor](https://www.raptorservices.com/). -This approach improves performance and reliability when processing large amounts of CDP user records. -For more information, see [Background tasks: How it works](background_tasks.md#how-it-works). - -By using Messenger while working with large batches of data, requests are queued instead of being processed synchronously: - -- queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) -- every single data is recorded in the database -- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger](https://symfony.com/doc/current/messenger.html) configuration -- processing happens at set intervals to avoid timeouts and keep the system stable - -Follow the [database update procedure](https://doc.ibexa.co/en/latest/update_and_migration/from_5.0/update_from_5.0/#database-update) to proceed. - -1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. - -2\. Add `bulk_async_threshold` setting in the `config/packages/ibexa_cdp.yaml` configuration: - -``` bash -ibexa_cdp: - bulk_async_threshold: 100 # Default: 100 items -``` - -Available options: - -- `bulk_async_threshold` (integer, default: 100) - minimum number of items required to trigger asynchronous processing - - below threshold - items are processed immediately in a single request, using the standard synchronous behavior - - at/above threshold - items are automatically dispatched to the asynchronous queue for background processing - -3\. Make sure that the [worker starts](background_tasks.md#start-worker) together with the application to watch the transport bus: - -``` bash -php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenger.bus -``` - -For more information, see [Start background task worker](background_tasks.md#start-worker). diff --git a/docs/update_and_migration/from_4.6/update_from_4.6.md b/docs/update_and_migration/from_4.6/update_from_4.6.md index b283ed4a9b..dd9a112d0e 100644 --- a/docs/update_and_migration/from_4.6/update_from_4.6.md +++ b/docs/update_and_migration/from_4.6/update_from_4.6.md @@ -566,17 +566,17 @@ If you do, add the required dependencies to your project: composer require guzzlehttp/guzzle:^6.5 php-http/guzzle6-adapter:^2.0 ``` +### Messenger support in CDP + +If you're using [CDP](cdp.md) and haven't configured Ibexa Messenger yet, do so now. +Follow the [Messenger setup instructions](https://doc.ibexa.co/en/4.6/infrastructure_and_maintenance/background_tasks/#install-package) to continue. + [[% include 'snippets/update/notify_support.md' %]] With the product updated to the latest version, you can now finish the update process or proceed to updating the LTS Updates packages. -### Messenger support in CDP - -If you are using CDP and have not configured Ibexa Messenger yet, do so now. -Follow the [Messenger setup instructions](https://doc.ibexa.co/en/4.6/infrastructure_and_maintenance/background_tasks/#install-package) to continue. - ## LTS Updates [LTS Updates](https://doc.ibexa.co/en/4.6/ibexa_products/editions/#lts-updates) are standalone packages with their own update procedures. From 2125b902641c5db9720223e6e9370a0f14f98b80 Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Thu, 5 Feb 2026 11:06:39 +0100 Subject: [PATCH 09/12] fix --- docs/cdp/cdp_activation/cdp_data_export.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index de2d6c020f..60e6e47a09 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -144,11 +144,9 @@ By using Messenger while working with large batches of data, requests are queued - queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) - every single data is recorded in the database -- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger](https://symfony.com/doc/current/messenger.html) configuration +- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger]([[= symfony_doc =]]) configuration - processing happens at set intervals to avoid timeouts and keep the system stable -Follow the [database update procedure](https://doc.ibexa.co/en/latest/update_and_migration/from_5.0/update_from_5.0/#database-update) to proceed. - 1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. 2\. Add `bulk_async_threshold` setting in the `config/packages/ibexa_cdp.yaml` configuration: From 4a035ecff8a08fd7dedd4993be6312b5b2866d3a Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Thu, 5 Feb 2026 11:11:15 +0100 Subject: [PATCH 10/12] code fix --- docs/cdp/cdp_activation/cdp_data_export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 60e6e47a09..37add712fe 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -186,7 +186,7 @@ It can be configured in both `dev` and `prod` environments, for example: ```yaml monolog: - handlers: + handlers: cdp_webhook: type: stream path: "%kernel.logs_dir%/cdp_webhook_%kernel.environment%.log" From c397b9c43711c6103ff51db3037e63c92c6c5fb2 Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Thu, 5 Feb 2026 11:28:38 +0100 Subject: [PATCH 11/12] link fixed --- docs/cdp/cdp_activation/cdp_data_export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 37add712fe..096237740b 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -144,7 +144,7 @@ By using Messenger while working with large batches of data, requests are queued - queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) - every single data is recorded in the database -- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger]([[= symfony_doc =]]) configuration +- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger]([[= symfony_doc =]]//messenger.html) configuration - processing happens at set intervals to avoid timeouts and keep the system stable 1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration. From 2f9cf45d68126a978609fd2148fda3153c8b97ee Mon Sep 17 00:00:00 2001 From: julitafalcondusza Date: Thu, 5 Feb 2026 11:40:05 +0100 Subject: [PATCH 12/12] link fixed --- docs/cdp/cdp_activation/cdp_data_export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/cdp/cdp_activation/cdp_data_export.md b/docs/cdp/cdp_activation/cdp_data_export.md index 096237740b..6b4b417e53 100644 --- a/docs/cdp/cdp_activation/cdp_data_export.md +++ b/docs/cdp/cdp_activation/cdp_data_export.md @@ -144,7 +144,7 @@ By using Messenger while working with large batches of data, requests are queued - queuing items starts automatically once a certain number of actions is reached (below this number, items are processed in a single request, using the standard synchronous behavior) - every single data is recorded in the database -- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger]([[= symfony_doc =]]//messenger.html) configuration +- a background worker retrieves records from the queue, processing them one by one or in batches, depending on the [Messenger]([[= symfony_doc =]]/messenger.html) configuration - processing happens at set intervals to avoid timeouts and keep the system stable 1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration.