Still stuck? Let’s figure it out.
Search the maintained answer bank first, then submit the exact problem when no resource solves it.
Go to the question form5 resources for “My Adalo list does not show the expected records. ”
These answers already cover parts of your question.
Tell us what went wrong.
Include the result you expected, what happened instead, and what you have already tried. Specific failures make much better answers.
Need paid help with an existing business app?
For an Adalo app your business relies on, Rehost offers ongoing management for fixes, releases, and integrations.
This is optional and separate from submitting a question. Opening Rehost does not send your question or email.
Explore paid helpHelp us understand what happened.
The most useful question says what should have happened, what happened instead, and which record or user was involved. “My list is broken” leaves several layers open. “The logged-in user should see only joined events, but every event appears after I add the relationship filter” identifies the expected result, visible failure, and likely data boundary.
Include the collection names, relevant property types, relationship direction, screen data, filters or conditions, and action order. Mention whether the behavior appears in Preview, a published web app, or a native build. If the failure changes after navigation or refresh, say so, that often distinguishes temporary component state from data that was actually saved.
Do not submit passwords, API keys, private user records, or screenshots containing sensitive information. A tiny anonymized example with two users and three records is usually more diagnostic than a full production database. Questions help prioritize future answers, but submission does not promise private support or a response on a particular schedule.
Before sending, reproduce the problem once with the simplest possible data and note the last step that still behaves correctly. Include that boundary in the message.