Publishing on Twitter problems

[roelbeckers1981]

Hi all,

Today I started to configure Adobe Campaign to publish to Twitter.

I followed these guides from Adobe docs:

• Publishing on Twitter (Config) and
• Publishing on Twitter (Delivery)

When I go to the Preview-tab in the Delivery I always get this error:

What I understand is that it refers to the Consumer Key from the Twitter app, which I've copied into the Adobe Campaign Service.

Anyone any clue why this error is showing?

All feedback is appreciated.

Thanks!

Roel

[Amitdeol · Accepted solution]

Hi Roel,

it is happening because Maybe you are using nms:recipient as your target mapping in delivery.

Switch that to nms:service and select the correct twitter account and it will go away.

if this is not the cause than can you post your workflow here? may be I can help you.

[Adobe_Campaing]

Hi Amitdeol, good afternoon,

It's like mine...

Error while evaluating document

JST-310000 Error while compiling script 'content htmlContent' line 41: recipient.relClientVehicule_client.vehicule is undefined.

SCR-160012 JavaScript: error while evaluating script 'content htmlContent'.

But i've already switched delivery and the problem still persist

:-(

Adobe Campaign​

[krvishaljha]

Answer to the error

"

Error while evaluating document

JST-310000 Error while compiling script 'content htmlContent' line 41: recipient.relClientVehicule_client.vehicule is undefined.

SCR-160012 JavaScript: error while evaluating script 'content htmlContent'."

The error you observed is a timeout issue when the workflow is trying to contact the deliverability server for fresh rules.

As there is a single deliverability server present for Adobe and all Adobe customers connect to it for new data, at times the web module gets overloaded on Adobe Servers and it results in a timeout. The code of this workflow when executed puts the current execution in a pause of XXXX seconds. This value is determined randomly and hence all our customers get a different wait time but still at times it cause bottleneck on our side leading to issues.

First step to try here is to restart the workflow manually and force execute it to see if it works then.

[pennyhardesty]

Thanks Roel! Ran into this issue as well and your answer fixed it. Much appreciated!