user\_metadata.recaptcha value is too long (max length: 500)
i’ve implemented recaptcha v3 with my web application by attaching the recaptcha token to the user\_metadata on sign up and login flows. i then pick it up with a pre-registration hook and handle it from there. it was working for nearly a year and i just had a bug reported saying it isn’t working. i t…
hey [@skyler.sorensen](/u/skyler.sorensen), welcome to the auth0 community!

this error is appearing because of the following limitation:

[image]

[metadata best practices](https://auth0.com/docs/best-practices/metadata-best-practices#metadata-storage-and-size-limits)

best practices for metadata in auth0.

metadata is allowed 10 strings with max 500 chars. may be you can breakdown …
your license should match the number of users on your system, so you may need to request a new license.

this command can be used to reset a password: <https://docs.mattermost.com/administration/command-line-tools.html#mattermost-user-password>. i suspect that the resource\_exhausted message may have originated from a back-pressuring committer node ([code](https://github.com/digital-asset/daml/blob/926fb5997a795e7f80443a9a3ba7898b1568d158/ledger/participant-integration-api/src/main/scala/platform/apiserver/services/apisubmissionservice.scala#l155-l157)). if that’s the case, i believe the approach should be the same: change the configuration if you need and make sure to handle those errors with the appropriate retry strategy. we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: May be the function is executed before the document is ready.
Try to use document.ready function like this:



```
$( document ).ready(function() {
    $('#machines').change(function() {
        var $selected = $(this).find(':selected');
        $('#description').html($selected.data('description'));
    }).trigger('change');
});

``` it looks like you are hitting lambda limit: 
<https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html> 
invocation payload (request and response) 
6 mb (synchronous) 
256 kb (asynchronous) 
can you please try to make chunks smaller and try again hi james,

as you already figured out, custom transactions does not support automatic instrumentations (xhr, fetch, resources) which means the user would have to start span and attach it to the transaction manually.

and yes by setting { managed: true } in the starttransaction option the transaction… hi erin

a website restart is required to pickup some changes to settingitems in the portal, id recommend giving it a restart and it should show.

regards
joe hey! your token request has been successfully added to the [accointing.com](http://accointing.com) database. it should be available today at 11:00 p.m. gmt. (7 a.m. et) We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1. What problem are you facing? Post the error that you get.  

Also please edit your first post by aligning the code properly and wrap [code] tag so that it is easily understandable for us to analyze.