Adobe web sdk ECID delay from server

[KhurrathUl]

ECID delay from server is causing the rule to time out which fails the rule from firing 

ECID delay error in console : watchConsoleLogs.8258a5d6.js:4 [alloy] [Identity] Delaying request while retrieving ECID from server.

error in console for rule :

Failed to execute "Send event" for "test" rule. A timeout occurred because the action took longer than 2 seconds to complete.
Error: A timeout occurred because the action took longer than 2 seconds to complete.

Context: 

• we are using a CNAME and i am currently based in Indian Standard timezone
• US folks do not get the ECID delay error and the rules are firing for them as expected

Is there any reason as to why this is happening and how can we fix this ?

[Devyendar]

@KhurrathUl  you can try this,

• Validate the cname path (check for redirects/misroutes) and that edgeDomain is pointing to the Adobe-provided host.
• Add delay to your rules
• Make sure to initiate Adobe Launch tags at the top of the page even within Header tag, which gives Edge library time to resolve ECID sooner
• If you are using Alloy then try to prime identity call earlier right after configure, so ECID is ready for events fired y your rule anything else

[bjoern__koth · Accepted solution]

Hi @KhurrathUl 

Those delays and failed rule executions sometimes do happen and to this day  have not fully been able to figure out why. I have seen them occur in various client projects, and small, and this is presumably rather an issue in the Adobe Edge network.

This has nothing to do with ECID as such imho. Also note that the ECID gets implicitly added to every Web SDK call, so there is no real need to request it separately.

If you need to map it on some XDM schema field, I would rather do that in the datastream mapping instead of making a getIdentity call