Why an Entry Might Not Be Accepted
Why an Entry Might Not Be Accepted
Every so often, you'll submit something and Psalmlog will ask you to try again instead of returning guidance. It isn't a bug, and it usually isn't anything you did wrong — it just means what you wrote sits outside what Psalmlog is built to respond to.
Here's what each message means and what will work instead.
Nothing you wrote is lost. Your text stays in the editor so you can adjust it and submit again.
"Psalmlog reflects on your own experience rather than looking verses up"
What happened: Your entry read as a request to find or explain a passage — something like "what does Romans 8:28 mean" or "find me verses about patience."
What to do: A Bible search or YouVersion will get you there faster. But if that passage is on your mind for a reason, that reason is worth writing about. Try: what's going on that brought this verse up?
You can also explore Scripture directly inside Psalmlog with the Bible reader, and tag passages onto an entry you're writing.
"Psalmlog is for praying and reflecting through your own life, not for general questions"
What happened: Your entry read as a question looking for an answer — advice, facts, or a recommendation — rather than a reflection.
What to do: If the question is genuinely weighing on you, there's almost always a reflection underneath it. Write that instead: what you're hoping for, what you're afraid of, what you'd want God to say about it.
"This looks like writing from somewhere else"
What happened: The text appeared to be copied in from another source rather than written by you — an article, a devotional, a passage of someone else's writing.
What to do: Put it in your own words. If a devotional or sermon moved you, write about what it stirred up — that's the part guidance can actually meet you in.
"There isn't quite enough here to reflect on yet"
What happened: There wasn't enough in the entry to build meaningful guidance from. A few words, a single fragment, or placeholder text will land here.
What to do: Add a few sentences about what's actually going on — what happened, how you're feeling about it, what you're bringing to God. Entries need at least 15 words, though a little more usually makes the guidance noticeably better.
"You've hit a temporary limit on submissions"
What happened: This one is about volume, not content — too many submissions in a short window. It says nothing about what you wrote.
What to do: Wait a few minutes and submit again. Your writing is safe.
"Please try sharing an authentic reflection"
What happened: This is the general message, shown when an entry doesn't fit any of the cases above.
What to do: Write a few honest sentences about where you actually are right now. If you're stuck, the journaling prompt on the entry screen is a good place to start — or choose a different focus and let its prompt carry your first sentence.
Why Psalmlog Draws These Lines
Psalmlog is a journal, not a search engine or a general assistant. Keeping the space narrow is what lets your guidance be specific to you — grounded in what you're carrying rather than answering a question anyone could have asked. The boundary is what makes the personalization possible.
Tips
- Write in first person. "I've been anxious about Friday" almost never gets stopped; "how do I stop being anxious" often does.
- Use the prompt. Each focus comes with a question designed to start you off in a reflective posture.
- Be specific about your own situation. Names, days, and details help — and they keep your entry firmly in reflective territory.
- Still stuck? Reach out to support and we'll take a look at what happened.
Next Steps
- Writing a Journal Entry — A full walkthrough of the session flow
- Using the Bible Reader — Explore Scripture and tag passages to your entries
- Understanding Your Guidance — What you'll receive once your entry goes through