Common questions

Why is a screen empty?

Check the environment, filters and date range first. The record might be in another view or still loading. If you see an error or an unavailable message, follow its instructions or ask for help before assuming there are no records.

Why do two numbers differ?

Start with the labels and dates. Are both numbers counting donations, or is one counting donors or enrollments? Check whether Cumulative is on and when the figures were updated. Revenue, received deposits, events and delivery attempts all measure different things.

Can we test without the Simulators screen?

Yes. The sandbox testing guide lists the supported API simulations, prerequisites and expected results. Your developer can call them directly or use a compatible API MCP tool. These operations are not available in production.

Are four passed checks enough to launch?

No. They show that four kinds of event reached the feed. Your team still needs to check its receiver, financial reports and ability to recover missed updates, then coordinate the launch with Roster.

Does “delivered” mean the donation reached the church?

No. In Webhooks, Delivered means your software acknowledged a message. You need separate bank information to confirm where the money is. A bank accepting a transfer is also different from confirming credit at the destination.

What should we include when asking for help?

Tell your Roster contact which screen and environment you were using, roughly when it happened, and what you expected to see. Include the relevant church, enrollment, event or request ID if you have it. Keep API keys, signing secrets, full bank details and identity documents out of the message. Use the contact options provided in the portal or by Roster.