suite submission failed
hi,

thanks for that. it worked. now i am getting a submit-failed error on all the tasks that use archer2. the error is as below:

[[error]](https://aws1.discourse-cdn.com/business20/uploads/cms_support/original/1x/af8cbf588f67b290c13245b2f33963a576fe8096.png "error")

given the error, i am not sure if i am doing anything wrong. could this be an issue to due having different usernames on archer and archer2?

regards,

daniel
hi daniel,

that error message indicates either a dodgey account code, incorrect queue for job size/time limits or exceeding number of jobs allowed.

you need to specify a valid account code. n02 is not a valid budget.

regards,

ros.
hey [@emartini](/u/emartini) ,

if you want to use clij2, you also need to activate the clij update site. the error should be gone then.

[[image]](https://aws1.discourse-cdn.com/business4/uploads/imagej/original/3x/0/9/095bc5fb3f3fa0db9dac6286bb16cf30ee81783d.jpeg "image")

see also the [installation instructions](https://clij.github.io/clij2-docs/installationinfiji).

let me know if this solves the issue!

cheers,

robert after further research and coming across [this answer to a similar issue](https://community.auth0.com/t/failed-silent-auth-login-required/33165/39), i made the switch to auth0’s custom domain solution and it fixed all of the issues mentioned above. this topic can be closed! thanks for getting back to me [@michel1](/u/michel1)! in this case, i recommend you to contact our support team: [how to contact our support team ✉](https://forum.asana.com/t/how-to-contact-our-support-team/87774). unfortunately i don’t have the tools in the forum to check what’s causing the error in your screenshot but our support team should be able to assist here.

when you c… 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. hi [@dr\_rainer\_demski](/u/dr_rainer_demski), welcome to the asana community forum :wave:t2:

in this case, i would suggest reaching out to our support team with the unique error code received as mentioned in the pop-up :slight\_smile:

you can reach out to the support team by clicking the support form prompt in the pop-up … was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . hey [@j.kassner](/u/j.kassner),

please see the solution to your question here:

[image]

["signuture is invalid" cdn 1.7.10 js viewer](https://devforum.zoom.us/t/signuture-is-invalid-cdn-1-7-10-js-viewer/24302/4) [web sdk](/c/web-sdk/13)

hey [@j.amelsberg](/u/j.amelsberg),

it appears you are using your sdk app key and secret to generate the signature. you need to use your jwt key and secret app to ge… since the error is on websockets, it is almost certainly a proxy layer somewhere that doesn’t support websockets, which is different on the two clusters (i.e. between you and any jupyterhub’s proxy-public entrypoint, rather than any part of jupyterhub itself or any of jupyterhub’s own configuration)… a search for other 1106 error posts shows you really do need to contact support, as it says. 
[login to cloudflare](https://dash.cloudflare.com/login) and then [contact cloudflare support](https://dash.cloudflare.com/?account=support) by clicking on the get more help button. hola, acabo de solucionar mi problema

problema:

[unhandled promise rejection: error: no native splash screen registered for provided activity. please configure your application’s main activity to call ‘splashscreen.show’ ([https://github.com/expo/expo/tree/master/packages/expo-splash-screen#-config…](https://github.com/expo/expo/tree/master/packages/expo-splash-screen#-configure-android)