Unexpected Application Error! and also "Invalid Sign In Up Params"
Hey there,
We upgraded to 0.4 which works fine (on my local machine here). However, When I am trying to log in over my other device, a laptop (which I was successfully logged in previously) , I get an errormessage "Invalid sign In up params". When trying to directly navigate to the content, customized objects, I receive an application error: Unexpected Application Error! Object metadata item not found for multipliers object Error: Object metadata item not found for multipliers object Here are Server logs from the worker container: [Nest] 34 - 01/29/2025, 10:31:44 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80 [Nest] 34 - 01/29/2025, 10:31:50 AM LOG [CallWebhookJobsJob] CallWebhookJobsJob on eventName 'note.updated' triggered webhooks with ids [ "f35027ff-17c3-4641-9708-a19aadbc2f6e" ] [Nest] 34 - 01/29/2025, 10:31:50 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80 [Nest] 34 - 01/29/2025, 10:31:50 AM LOG [CallWebhookJobsJob] CallWebhookJobsJob on eventName 'note.updated' triggered webhooks with ids [ "f35027ff-17c3-4641-9708-a19aadbc2f6e" ] [Nest] 34 - 01/29/2025, 10:31:50 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80 [Nest] 34 - 01/29/2025, 10:32:02 AM LOG [CallWebhookJobsJob] CallWebhookJobsJob on eventName 'note.updated' triggered webhooks with ids [ "f35027ff-17c3-4641-9708-a19aadbc2f6e" ] [Nest] 34 - 01/29/2025, 10:32:02 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80
We upgraded to 0.4 which works fine (on my local machine here). However, When I am trying to log in over my other device, a laptop (which I was successfully logged in previously) , I get an errormessage "Invalid sign In up params". When trying to directly navigate to the content, customized objects, I receive an application error: Unexpected Application Error! Object metadata item not found for multipliers object Error: Object metadata item not found for multipliers object Here are Server logs from the worker container: [Nest] 34 - 01/29/2025, 10:31:44 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80 [Nest] 34 - 01/29/2025, 10:31:50 AM LOG [CallWebhookJobsJob] CallWebhookJobsJob on eventName 'note.updated' triggered webhooks with ids [ "f35027ff-17c3-4641-9708-a19aadbc2f6e" ] [Nest] 34 - 01/29/2025, 10:31:50 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80 [Nest] 34 - 01/29/2025, 10:31:50 AM LOG [CallWebhookJobsJob] CallWebhookJobsJob on eventName 'note.updated' triggered webhooks with ids [ "f35027ff-17c3-4641-9708-a19aadbc2f6e" ] [Nest] 34 - 01/29/2025, 10:31:50 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80 [Nest] 34 - 01/29/2025, 10:32:02 AM LOG [CallWebhookJobsJob] CallWebhookJobsJob on eventName 'note.updated' triggered webhooks with ids [ "f35027ff-17c3-4641-9708-a19aadbc2f6e" ] [Nest] 34 - 01/29/2025, 10:32:02 AM ERROR [CallWebhookJob] Error calling webhook on targetUrl 'testurl.pruve.org': Error: connect ECONNREFUSED ::1:80
9 Replies
Hi, the worker is actually running asynchronous jobs. It should not raise issues when you navigate through the app
Could you rather share your server logs ? Unless you only see the
Object metadata item not found for multipliers object in console?We also changed the token expiration to 7D to make systen much more usable, maybe this helps as additional information
Invalid sign in up params
@AMoreaux could you have a look? 🙏Hello @armochillo
Could you confirm me that you sign in with an existing user in an existing workspace please?
@AMoreaux Yes, correct, I am signing in with an existing user in an existing workspace
I believe the issue is centered around the fact that another device still has a valid token and I assume the system is not able to create a new, valid token.
I assume this because right now; i ran into the same issue on the other device (which worked flawless in past 6 days), but today, token expired, and I am not able to log in due to same error message, so I am currently locked out of system 😦
We are running on version 0.4
You use the v0.40.0 ?
Are you available for a quick call ?
sure!