I’m facing a critical issue with the “Add Logged In User” action in my app. This action used to work perfectly but now it throws errors:
Unauthorized” in some cases
or “Internal Server Error” when I modified the permissions
What I’ve already checked:
The user is properly logged in
All collection permissions (Users and related ones) are set to “everyone can create/update/delete”
The relationships are correctly configured (many-to-many)
No custom visibility or privacy rules are blocking access
I tested the issue with a *new collection, → the same problem occurs
but I tested in a **new app, and it’s work, so the problem it’s just in my app
Important note:
The action still works on one old collection (called “Covoiturage”) created months ago, but any new collection or setup fails, even with identical settings.
This seems to be a recent change or a backend bug on the platform.
Anyone else experiencing this?
Thanks in advance for any help or insight!
Welcome to the forum!
Sorry to hear about your issue. In general, you can see more details about such errors in browser console log (in Chrome is’s View → Developer → Javascript console), in the console tab or network tab (there you can see which queries are sent, their payload and response).
But if you’ve checked that app setup is correct (as you mention in your post), then there is a probability that something is wrong with the app itself. I’d recommend submitting a ticket here: https://info.adalo.com/submit-a-support-ticket.
