Rochelle,
Allen hit my first check point on the head - is it a net new lead or contact created directly by Eloqua? The activity calls are triggered by the action itself, regardless of the status of the contact in CRM, so it fires as soon as it registers the action, regardless of CRM ID being associated to the Eloqua contact. To my knowledge, it's even regardless of processing steps - the only dependency to the activity call firing is the activity registering in Eloqua. My second check point for this issue would be checking for duplicate records in SFDC - duplicates leads or duplicate contacts. If they exist, the ID's may be updating in Eloqua based on the last modified date on the CRM record, which causes all kinds of chaos in terms of activity history tracking and reporting in CRM. You'd see the activity in Eloqua and then only see it on the matched (via CRM ID) record in CRM. Finally, confirm that all activity calls are working - is it only the form submit activity call having an issue or also website visits? We only write form submits and website visits, but you might also be writing email click-throughs, etc... That will help narrow your troubleshooting as well.
If those check points pass, and there's not another identifiable pattern based on your testing, I'd recommend you contact Support as they'd see any possible issues on the back-end of the system.
I'm glad to help as needed, keep us posted.
Best,
Kristin
