Support, troubleshooting, and known issues

When a known limit is still okay

Some known limits are real, but still compatible with safe trial progress when they do not block the main decision your church is trying to make.

Who this is for: Users deciding whether a known product limit is acceptable friction or a reason to pause evaluation.

Last reviewed 2026-04-30 · Source of truth: broader help library · Languages: en, es

Article metadata

Product area: known limits and product boundaries

Owner: Launch readiness

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

What to expect next

Keep moving when the limit is explicit, low-consequence, and not central to your decision.
Escalate when the limit starts affecting trust, migration readiness, or a real operational commitment.

When the limit is minor friction

A known limit may still be acceptable when it does not distort the main trial question, does not create sensitive risk, and does not block the next important operational step.

Minor friction is easier to tolerate when the boundary is explicit, the consequence is low, and the product is not pretending the gap does not exist.

How to keep evaluating safely

Keep evaluating when the known limit is visible, bounded, and not the deciding factor for migration confidence, launch readiness, or stakeholder trust.

The goal is not to ignore the limit, but to place it at the right level of consequence instead of treating every gap as a showstopper.

Escalation path

If you are no longer deciding whether the limit is acceptable friction and are now deciding whether it undermines the whole evaluation, move into guided or structured follow-up.

Related next steps

Read current scope vs future possibility Read when a known limit becomes a real blocker Open Spanish version Back to help center