Error while accessing Inbox

[Matteo]

Hello.

Since a few weeks (not sure exactly) we’re experiencing a problem while accessing a specific inbox. But if we access the segment the inbox is built upon, there’s no problem at all.

Here’s the evidence:

And in the browser console we find this runtime error:

I don’t understand what’s wrong. This only happens with our “Template” inbox. And this only happens in PROD environment.

May you please help to understand what’s wrong?

• Agent technology: nodejs
• Agent (forest package) name & version (from your .lock file): @forestadmin/agent - version 1.66.0

[anthony.guimard]

Hello @Matteo,

Thanks for reporting this. We can see the issue on our side too, the team is looking into it right now.
We’ll update you once we have a fix ready.

Anthony

[anthony.guimard]

Hi @Matteo,

We’ve released a fix for this issue.
Let me know if everything is now working correctly on your end.

Edit: A regression has been noticed during the attempt to release the fix. we’re working on a fix, keep you update

Anthony

[Matteo]

Ok @anthony.guimard
In fact, I was about to tell you that on my end everything has stayed the same as before

Thank you for your message and the edit. let me know when you’ll need me to have a check on my side

Thank you!

[anthony.guimard]

Hello @Matteo ,

Sorry for the wait. A fix was released earlier this week, and everything should now be back to normal. Could you confirm that you’re no longer able to reproduce the bug on your side?

Anthony,

[Matteo]

Hey @anthony.guimard, unfortunately I’m still experiencing the same issue on my end
I’d much rather be giving you good news, but it’s still there.

Let me know if there’s any other check I can run on my side.

(this is after an empty cache and hard reload in chrome dev tools > console)

[Matteo]

…And it seems like it’s not related to any elements that might be in the to-do inbox.

Hope this helps

[shohanr]

Hi @Matteo ,

I will take the hand on this subject.
Could you please provide me these information:

1. Project name
2. Team name
3. The user name with who this issue appears (please provide me multiple emails if you have this issue with several users)
4. The collection name of this segment

I would also like to know if users are manually assigned or if it is always through self “Start processing” ?

Best regards,

Shohan

[Matteo]

Hello @shohanr! I’m happy to help and I really hope I can be useful.

If you don’t mind, I’d rather answer some of your questions privately and just leave the non-sensitive stuff here, so this thread can work as a proper knowledge base too.

Project, Team, User, Collection names shared privately (in a few minutes)

About the users question: I honestly assumed it was something that happened to everyone. But now you’ve got me wondering… Actually, I couldn’t check with all my users on such short notice, but I’ll try to quickly reach out a couple of them, to confirm. At the moment, I’m just sure that 2 users are affected, me and [undisclosed - shared in private].

I would also like to know if users are manually assigned or if it is always through self “Start processing”?

Inbox items are pretty much always assigned manually by one user who acts as a manager and hands out tasks to the team (manager details in the private message).

I should also mention that, worried we might have messed something up when setting up the inbox, we tried deleting it and creating it again — but no luck, the error stuck around.

In a few minutes, I’ll privately share all the required info.

Thank you!
Matteo

EDIT: I’ve just sent you a private message with all the required information

[Matteo]

Hey @shohanr I don’t know what kind of magic you pulled, but whatever you did seems to have worked. The problem is now gone.

I’ll still share the requested info privately… but in the meantime, thanks for the fix

[shohanr]

Hi @Matteo ,
I am glad it fix your issue.
I am off tomorrow but will take a look at your message on Friday,

Best regards,

Shohan