ACC does not rely on SMB that I know of, obviously if you would like a more official answer you need to raise a ticket to Adobe TechOps. Also, if there was any ACC feature making use of SMB; it would've been updated/patched long ago and mentioned in the release notes as SMBv1 was deprecated in 2013....

What is a cell code? You can add a "Delivery Code" to make it easier to identify multiple deliveries which belong to the same delivery segmentation, so when you query your tracking data you add the condition "AND" @deliveryCode = xxxi.e preblackfridayEN and preblackfridayFR  

The IE engine in ACC is very old and outdated, looks like your js script is having compatibility issues and I don't think there is a way around this. You may check the following links for further supporthttps://experienceleaguecommunities.adobe.com/t5/adobe-campaign-standard/adobe-rich-client-browse...

Which instance is being affected? your on-premise marketing instance? for these kind of issues only Adobe TechOps can help. You could liaise with your db administrator to correlate database performance during execution of this particular procedure or setup a monitoring job to check for long running ...

In order to know how any changes/updates have affected your instance we need to know your acc server/client version as well as hosting design. You may check in the release notes to see if there are any updates relevant to your version https://experienceleague.adobe.com/docs/campaign-classic/using/re...

Do you mind sharing the error? You can set the number of messages as a fixed number or percentage as stated in the waves definition form  

You can use the @eventDate of the Recipient delivery log (nms:broadLogRcp) to estimate down to individual email records. You can look at the following test i sent to my self and check the timeline on the timestamps The latest event date on ACC is 02/12/2021 04:59:20 and I received the email in my in...

Something like this?? Query the Recipient tracking logs (nms) nms trackingLogRcp  Here is the XML configuration of the activity   <query collision="0" distinct="true" img="nms:activities/query.png" keepAllExtraData="false" label="undefined" mask="0" name="queryCountURL" noAutoPk="true"...

You can use queryDef to fetch workflow details var query = NLWS.xtkQueryDef.create( {queryDef: {schema: "xtk:workflow", operation: "select", select: { node: [{expr: "@id"}, {expr: "@label"}, {expr: "@internalName"}] }, where: { condition: ...

perhaps @Vipul_Raghav can provide some details as he works closely with the engineering team.