function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Jennifer BabinJennifer Babin 

The value of the "to" parameter contains a character that is not allowed or the value exceeds the maximum allowed length.

Hi there,
I'm having issues completing a hands-on-challenge due to receiving the following error message:

The value of the "to" parameter contains a character that is not allowed or the value exceeds the maximum allowed length. Remove the character from the parameter value or reduce the value length and resubmit. If the error still persists, report it to our Customer Support team. Provide the URL of the page you were requesting as well as any other related information.

I've tried changing all the fields and also tried the challenge in a different browser. 
Does anybody know how to overcome this issue?
Thank you
SandhyaSandhya (Salesforce Developers) 
Hi,

Refer below salesforce help article for resolution.

https://help.salesforce.com/articleView?id=000213842&type=1 
 
https://success.salesforce.com/answers?id=9063A000000DmLrQAK
 
Please mark it as solved if my reply was helpful. It will make it available for other as the proper solution.
 
Best Regards
Sandhya
 
Jennifer BabinJennifer Babin
Hi Sandhya,

Thank you for your reply. I have followed your links and the instructions and I am still experiencing the same problem. 
I am using the trailhead platform, does this have anything to do with it?

Thank you
Kind regards,
Jennifer Babin
Bernd WenerBernd Wener

Hi there,

I am having the exact same error. I am trying to add an object with the schema builder in a trailhead playground I created for the "Schema Builder" module: https://trailhead.salesforce.com/de/content/learn/modules/data_modeling/schema_builder
When I want to save the object, I get the exact same error as Jennifer described.

Using Chrome version 79.0.3945.79 (64bit) on Windows 10

Any hints?

Thanks in advance,
Bernd

Bernd WenerBernd Wener

Ok, restarting the browser did the trick :)