Skip to main content

Updates not showing

If you've made or expect to see a recent change — a new Mass time, an updated availability indicator, a confirmation email — and it's not showing up, the cause is almost always caching, a dropped real-time connection, or a publish state. Work through the quick checks first.

Quick checks​

  1. Hard refresh. Press Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows/Linux) to force the browser to reload without using the cache. This resolves most "I just saved this and don't see it" cases.
  2. Clear your browser cache for the parish site. In your browser's settings, clear cached files for the parish URL. Then reload.
  3. Sign out and back in. Sign out completely and sign back in. This refreshes your session and pulls the latest data.
  4. Try a private or incognito window. A clean browser session bypasses extensions, cached pages, and stored sessions, isolating the cause.
tip

On phones, closing and reopening the tab usually isn't enough — close the entire browser app from your app switcher and reopen it. Mobile browsers cache aggressively.

Common causes​

A schedule change isn't visible on the public page yet​

Public-facing pages may serve briefly cached versions for performance, typically for under a minute. Wait 30–60 seconds and refresh. If the change still doesn't appear after a few minutes, the issue is likely something else — see the admin section below.

A new Mass intention was added but the requester says they didn't see a confirmation​

Confirmation emails arrive within a minute or two in normal conditions. If a requester reports not seeing one:

  • Ask them to check their Spam or Junk folder.
  • Confirm the email address on file is correct and current — typos and old addresses are the most common cause.
  • Check the receipt directly via the requester's dashboard. See Payments, invoices, and receipts.
  • If the email is correct and there's still nothing, an administrator can resend the confirmation from the intention record.

My phone shows old data, but my computer shows new data​

This is almost always a service-worker / Progressive Web App cache. Sacramentum can be installed as a PWA on phones for fast, app-like access, and the PWA caches assets to keep working offline.

To force a refresh:

  1. Close every Sacramentum tab on the phone.
  2. Quit the browser app from your app switcher (don't just background it).
  3. Reopen the browser and visit the parish URL again.

If you have Sacramentum installed as a home-screen app, removing and reinstalling it from your parish site clears the cache fully.

Real-time priest availability isn't updating​

The "Available now" indicators on the parish home page are powered by a live connection. If the connection drops (because of a network change, sleep mode, or a long-idle browser tab), the indicator can freeze on the last known state. Refresh the page to reconnect. If you switch networks frequently — for example, between Wi-Fi and cellular — expect to refresh after the switch.

Items in my shopping cart disappeared​

When you add a Mass intention to your cart, Sacramentum reserves the date and time slot for two minutes so no one else can book it while you check out. If you don't complete checkout within that window, the reservation expires and the slot is released. Your cart items disappear because the slot is no longer held for you. Re-add the items and complete checkout promptly. See Cart and checkout.

A draft form or schedule isn't appearing publicly​

Drafts are admin-only by design — they don't appear to parishioners until they're published. If you (as an admin) created an online form, schedule, or other parishioner-facing item and parishioners report not seeing it, open it in the admin console and verify it's in the Published state, not Draft.

When you're an administrator and the issue is yours to fix​

"I edited a recurring schedule but old events still show the old times"​

Recurring schedule rules generate concrete Mass and confession events in advance. Editing the recurring rule does not automatically regenerate already-created events. Either delete and regenerate the affected events, or use the regenerate option in the schedule editor. See Managing schedules.

"A Stripe payment came in but didn't post to the ledger"​

This usually means a webhook delivery failed. Webhook health is visible in the payment configuration tab in Settings. If webhooks are unhealthy, you can reset them from the same panel — Sacramentum will reconfigure the Stripe webhook endpoint and retry pending events. See Payment configuration.

"I deactivated a user but they can still see admin pages"​

Sessions persist until they expire. The user will lose access at their next sign-in or session refresh, but if they're already signed in they may continue to see cached data briefly. To remove access immediately, ask the user to sign out, or coordinate with them on next sign-in.

warning

If you suspect a security issue (compromised account, unauthorized changes), don't wait for sessions to expire. Reset the affected user's password and contact your parish administrator or Sacramentum support.

When to contact your parish administrator​

If you've worked through the quick checks and the relevant common cause and the data is still stale, contact your parish administrator. Include:

  • The exact page URL where the issue appears
  • What you expected to see, and what you're seeing instead
  • When the change was originally made (if known)
  • Whether the issue is on one device or across all devices
  • A screenshot if possible