Hi Von, Could you tell me more about your Joget setup? Are you running it on multiple nodes/clusters? This kind of behavior often pops up when sessions aren't being persisted properly across the system.

A few questions that would help us debug:

• How often does this happen? Every time or just occasionally?
• Have you tried this in different browsers to see if the behavior's the same?
• Could you check the logs to see if there are any session-related / any other errors when this occurs?
• Are there any form permissions set on the object you're trying to access? 

If you could share more details, it would be really helpful in pinpointing what's going on. 

Hello Varnaa,

I am using Joget DX 7, and currently, I am the only user working with Joget. We are running it on a single server.

The issue happens every time.
I tested it in both Chrome and Edge, and the result is the same in both browsers.

I haven’t found any errors in the logs.
I’ve checked all permissions, and I should have access. Interestingly, I can open the page without any issues if I do not include the parameter.

Thank you for your answer

Any chance you could create a minimal version of the app that demonstrates this issue? 

I can't right now, sorry.

is the issue resolved at least? 

No, it still doesn't worke