The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Second week in which the system reports zero attendees
THREE PROBLEMS:
1) This is the second week in a row when our webinar shows as no ZERO ATTENDEES but in fact over 950 people attended. The webinar is:
Webinar ID
986-584-051
Because there...
Jamch we see that you have a current case open and our team is working on restoring your data. Your case will be updated once it's restored.
Fran_Simon we are currently reviewing the status of your case.
Please note:
- We are fixing the webinars that are missing data on a case by case basis.
- We have a fix for the Cancelled Registrations currently being reviewed. It is being treated as a high priority and we hope to release it soon. We will continue to update this thread on the status of the fix.
Thanks everyone for your patience and we apologize for the frustration and inconvenience.
Hi Fran_Simon, I reviewed your support tickets and I see support responded to you and that you confirmed the data was restored for the reports. This issue and the canceled registration issue are both high priorities for our developers and are being worked on currently. Are there any webinars that you still need reporting data for?
Glenn, right now I have a lag in webinars until after the holidays, thank goodness. Even though I have the data I need for the moment, I've been told the database disruption is not resolved, but the Support Agent closed the ticket and told me I can reopen it if it happens again. UMMMM. NO. The ticket should remain open until the database issue is resolved and customers can expect to not encounter this problem again. Here's what the agent said:
Our Engineering team hasn't fixed the issue for complete, however you can feel assured they're doing their best to prevent this in the future.
In case you're experience this problem again you can reopen this ticket at anytime and we'll recover the information.
How could it be possible that the database gets so disrupted with an update to the point that after almost two weeks it has not been resolved? I am frustrated with the lack of upfront and proactive communication and the lack of service.
Do you think this will be resolved by the start of 2023?
Hi Fran - with the vague communications it opens the door for one to wonder if there was a security incident here. GOTO - Was there any part of this that was related to a security issue?
