Skip to main content
Version: v72

v2025.2.72

v2025.2.72.0 – Redis Storage, Process Optimization​

Added​

Redis Storage​

For the correct functioning of the platform, it is now required to use Redis-compatible storage. Such storage:

  • enables a gradual transition away from file-based persistent storage;
  • increases the platform’s fault tolerance and manageability;
  • ensures more reliable and faster interaction between services.

We recommend using Kvrocks. The platform installation documentation includes a guide for connecting Kvrocks.

Using Redis is allowed but only with AOF data persistence mode or RDB + AOF mode.

Support for RabbitMQ Quorum Queues and Unified Virtual Host​

caution

Before installing the update, you need to create a new virtual host (by default, altcraft) and ensure that the current user has full permissions on it.

info

If there are messages left in old virtual hosts, you can use the Shovel plugin to transfer them. Below is an example of moving messages from the trk_read queue in the / virtual host to the altcraft virtual host:

rabbitmqctl set_parameter shovel trk_read '{
  "src-protocol": "amqp091",
  "src-uri": "amqp://altcraft:abcdefghijklmnopqrstuvwxyzABCDEF@localhost:5672",
  "src-queue": "trk_read",
  "dest-protocol": "amqp091",
  "dest-uri": "amqp://altcraft:abcdefghijklmnopqrstuvwxyzABCDEF@localhost:5672/altcraft",
  "dest-queue": "trk_read"
}'

Other Changes​

  • Users can now create a new report based on an existing one.
  • Added support for configuring a handler pool for the RMQ Event Sender.
  • The user session duration is now configured via the PROCAUTH_SESSION_TIME_SEC parameter, and the ability to continue the session when the IP address changes is controlled by PROCAUTH_SESSION_ALLOW_CHNET.

Improved​

  • Platform performance has been improved.
  • Stability of the procintegras process has been improved.
  • Task processing in the proctask process has been optimized.

Other​

  • Platform performance improved.
  • Fixed several UI/UX issues.
  • Increased stability of the procintegras process.
  • Fixed authorization-related errors.
  • Optimized task processing logic in proctask.
  • Fixed incorrect display of analytics metrics.
  • Confirmation link validation in templates works properly again.
  • Automation Scenario elements now operate more reliably — previously occurring errors have been resolved.
References

v2025.2.72.0: PL-18318 PL-18343 PL-18519 PL-18367 PL-18349 PL-18323 PL-18192 PL-18321 PL-18322 PL-18262 PL-18316 PL-18483 PL-18445 PL-18482 PL-18276 PL-18458 PL-18427 PL-18389 PL-18372 PL-18347 PL-18319 PL-18332 PL-18403 PL-18396 PL-18359 PL-18375 PL-18379 PL-18302 PL-18307 PL-18295 PL-18255 PL-17490 PL-17886 PL-18134 PL-17904 PL-16949 PL-16946 PL-17729 PL-17590 PL-16965 PL-17223 PL-15798 PL-17545 PL-17068 PL-17474 PL-17453 PL-17131 PL-17451 PL-17442 PL-17399 PL-16918 PL-17328 PL-17302 PL-16782 PL-17192 PL-17243 PL-17023 PL-16948 PL-17101 PL-17087 PL-17091 PL-11284 PL-16885 PL-17030 PL-17029 PL-16969 PL-17013 PL-6658 PL-16541 PL-16356 PL-16702 PL-3437 PL-16530

v2025.2.72.707 – Custom channel improvements, link shorter optimization​

danger

Pay attention to the important changes in the link shortener behavior:

  • The content of the web version of the message is now transmitted without modifications. This means that actions with it will appear in the profile card as content actions. Links to web versions are still transmitted with the dummy=1 parameter;
  • The link format has changed from ^(/s/[A-Za-z0-9_-]{5,20})$ to ^(/s[A-Za-z0-9_\-!~\.]{10,12})$.

Added​

  • Added dynamic display of process status when starting and stopping the platform using akd.
  • The number of profiles entered and exited is now displayed above scenario elements.
  • The variable insertion menu now includes scenario name and scenario ID, as well as element ID and element type.
  • Users can now override form templates using custom files.
  • Added a launch log for the trigger scenario element "Scheduled Capture".
  • The profile card now displays information about scenario errors if the profile was in the GKG.
  • API requests for the scenario list and template info now support updated_user and update_time parameters.

Improved​

Custom Channel Pipeline Improvements​

The operation of custom channel pipelines has been significantly improved. The following changes were made:

  • Fixed errors occurring during pipeline execution.
  • Added access to object names.
  • Pipelines can now accept event dates in the EventObject.
  • Added a unique message identifier in the pipeline, matching the ID in ClickHouse.

Other Improvements​

  • It is now possible to override the Firebase URL for each platform account in the configuration file.
  • The search and filtering interface across the platform has been updated.
  • Refactored link shortener operation. Duplicate link IDs were eliminated, and the maximum link length was reduced to 14 characters.
  • The maxAmountOfChanges constant was moved from segstat_recalc to a separate configuration parameter — SEGSTATIC_PROFILE_CHANGES_BATCH_SIZE.
  • Optimized the Best Send Time ML service. Related configuration parameters were also updated.
  • Improved platform performance.
  • Improved stability of procworkflow, webcontrol, and proctask processes.

Other​

  • Static segments created via API are now recalculated correctly.
  • Fixed incorrect calculation of segments with identical file names.
  • The last update date is now correctly displayed in profile databases.
  • The subscription capture trigger in scenarios now considers the selected channel and resource.
  • Fixed a JavaScript error on the campaign type selection page when creating a campaign from the calendar.
  • The session in the web interface no longer expires too quickly.
  • The adddate function now works correctly in the "API Call" scenario element.
  • The JSON filter now supports fields with underscores in their names.
  • Push templates imported via API can now be opened in the beta editor.
  • The not_strict and subscription_filter parameters in scenarios now work correctly.
  • AKMTA now correctly processes DSN when using the From field address in MAIL FROM.
  • Fixed 500 error when requesting the web version via API for profiles in the stop list.
  • Fixed an error that occurred when placing a pixel via the Tag Manager.
  • Fixed parsing of status responses from the SMSTraffic sender.
  • Phone numbers in .xls files are now parsed correctly.
  • The send_message_id value in custom JSON for Push now matches the send_message_id from the event capture hook.
References

v2025.2.72.707: PL-18764 PL-18548 PL-18710 PL-18763 PL-18671 PL-18659 PL-17043 PL-16495 PL-17891 PL-18293 PL-18486 PL-18752 PL-18674 PL-18761 PL-18095 PL-18634 PL-18661 PL-18548 PL-18531 PL-17937 PL-18383 PL-18264 PL-18449 PL-17595 PL-17827 PL-18750 PL-13124 PL-18737 PL-18070 PL-17894 PL-17772 PL-18132 PL-18672 PL-18703 PL-18712 PL-18669 PL-18619 PL-18613 PL-18648 PL-18546 PL-13124 PL-18573 PL-15659 PL-18734 PL-18705 PL-18693 PL-18668 PL-17784 PL-18662 PL-18608 PL-17418 PL-16610 PL-18697 PL-18043 PL-18685 PL-18683 PL-18676 PL-18656 PL-18605 PL-18524 PL-18660 PL-18658 PL-18447 PL-18494 PL-18632 PL-15330 PL-18592 PL-17661 PL-17120 PL-18534 PL-18446 PL-18304 PL-18261 PL-17705 PL-18417 PL-15337 PL-18164

*Meta Platforms Inc., the company behind Instagram, Facebook, and WhatsApp, has been designated as an extremist organization and is banned in the Russian Federation.
**Viber is a trademark of Rakuten Group, Inc. and is blocked in the Russian Federation.

Last updated on