Interactive Webinar Registration Error

[lmccracken]

I am testing out the interactive webinars with Adobe connect integration. I am using my own email accounts to test but after successfully registering with the email address once, I receive the "Registration Error" status for any consecutive registrations under the same email address. The status reason is 'Error registering with webinar provider. exception='Failed to get the data from connect'. 

When trying new email addresses the registration works correctly. Is this an issue with duplicates being created in Adobe Connect or is it a connection issue between Marketo Engage and Adobe Connect? 

[Michael_Florin]

The error message might not be perfect, but it's correct that Adobe Connect prevents one email address from registering more than once for one webinar session, isn't it? Or what would be the behavior you expect?

EDIT: I just learned that you also produce a registration error when a person is set to "Registered" who is already a presenter or a co-host in AC.

And by the way: Is there any way to see details of Registration Errors?

And btw2: Does Interactive Webinar come with trigger tokens for their various new triggers?

[Michael_Florin]

We've tested the scenario now, and you're right, @lmccracken, this is a problem.

If a person with the status "Registered" submits the registration page again, they are set to "Registration Error". That's a bug, and I'll file a support now to bring that to Adobe's attention.

Not only does this confuse your reporting, it also messes up with a potential webinar reminder email which we always send to everyone with the program status "Registered".

Also: It seems that Co-Hosts and Presenters can not register without being set to "Registration Error". Not that big a problem, but the error communication is not elegant.

EDIT: Marketo Support response here:

Our engineering team is aware of this issue in which a person who's already registered to a webinar can attempt to register again and doing so results in a registration error status. At the moment, they're developing a patch for this but I do not have an ETA of when this will be ready as it's still under investigation.