@Ken_Qrious: my bad, when I was in Adobe Support (until early 6.1 versions), the default value of this option was 50... But no Hypothesis feature was available for example

Hi @Ken_Qrious, I didn't see your last updates. I'm glad that you've been able to narrow the issue. I don't know why your option is set to "15" as normally it's set to "50" by default. It means that someone downsized the value and it could be interesting to understand why. Managing DB perf? I think ...

This is because you have to add internalName attribute in the additonal data of the query.

@Ofattah, frequency has nothing to do here... technical workflows such as operationMgt are querying the DB every 30 sec... You should involve your DBA and someone from network team in order to know from where the problem lies

Hi, I do not have ACC on this laptop unfortunately so I cannot develop it with you. But no, that's not the code at all I'm describing: you can inspire yourself about this code I've just wrote in notepad: var wkf2restart = NLWS.xtkQueryDef.create(<queryDef schema={vars.targetSchema} operation="select...

You could build a workflow that will scan all the "production" workflows status and use api command like:Restart (adobe.com)You create a workflow with the query activity linked to a JS activity.In the JS, you use a query def function with "vars.targetSchema" as schema declaration: it will select aut...

In fact that depends of the implementation architecture: in Adobe hosted environment, you'll get informations from Adobe and they'll ask you SMS provider informations. The IP address to be whitelist is the one from AC Server. You'll get informations here:https://experienceleague.adobe.com/docs/campa...

Hello, hyptothesis can depend about the option nmsOperation_limitconcurrency that is, by default, set to 50Depending of your implementation, hypothesis linked to operations (campaign module) can be delayed regarding the number set in this option but also any specific implementation hacks on the camp...

Hi, according to me, the first question to ask yourself is why to have to restrict business users on queries...If this is in order to do not be able to have access to data they should not see, a simple way to achieve that could be to use sysfilters on the schemas that are sensible. Filtering schemas...

you can do it even easier: https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-questions/how-to-launch-from-external-file-s-email-column/qaq-p/234146 just don't forget that through this external file mapping, you'll have to call your custom columns with "datasource.myCustomColumn...