Error: 'No more than 1024 characters' While Inviting the Attendees

ISSUE
Users encounter an error message stating 'No more than 1024 characters' when attempting to invite attendees to a meeting using the Webex meeting scheduler. This error occurs when adding attendees to a scheduled meeting.

Error: 'No more than 1024 characters' while inviting the attendees in a meeting scheduler:

User-added image

RESOLUTION
To resolve this issue and revert to the previous user interface for inviting attendees, which does not have this limitation, follow the steps below:
  1. Contact Webex Customer Success Manager
    1. Please reach out to your designated Webex Customer Success Manager (CSM) to talk about your issue with the meeting scheduler.
  2. Submit an Ops Request
    1. Please ask your CSM to submit an Operations (Ops) Request. The Ops Request should disable your Webex site's 'Simplified Alternate Host Selection' option.
  3. It is essential to understand that this setting cannot be disabled through the standard site administration portal. The Webex operations team must make the change.
  4.  If you require additional help or guidance, consult the Webex help article | How Do I Get Help with Webex? 
CAUSE
The error is caused by a limitation in the Webex meeting scheduler interface. The interface converts the input into a list display format when adding new attendees. This list display has a character limit of 1,024 characters for the Attendees field. If the combined length of the email addresses and any additional text exceeds this limit, the error message will be triggered, preventing the user from adding more attendees.

ADDITIONAL NOTES
Please keep in mind that requesting a change to the meeting scheduler interface may affect other functionalities related to the attendee invitation process. Discuss any potential impacts with your CSM before proceeding with the Ops Request. It is also recommended that the list of attendees be reviewed, and multiple invitations should be sent if the list is extensive as a temporary workaround until the issue is resolved.

 

Was this article helpful?