Raffle Operations templates and creation

Raffle Operations uses reusable community-owned raffle templates.

A template holds the repetitive raffle configuration for one community. Different communities can have completely different templates and Discord requirements.

Example

A managed community can have templates such as:

• Team
• Raiders
• Holders
• Community

Another community can use a completely different template set.

The important rule is that one community's template and Discord roles must not silently be reused for another community.

Project selection

When creating raffles, the manager selects an existing canonical project or provides the project information needed to create a new one.

Project information is separate from the raffle template so the same project can be reused across several community raffles.

Creating from the dashboard

Raffle Operations can create multiple raffle instances in one operating workflow while keeping each raffle independent.

Per raffle, the manager can use the selected community template and apply supported instance-level values such as:

• raffle title
• winner/spot count
• duration
• project X follow behavior
• project-specific description or context where available

A creation batch is an operation record, not a permanent raffle group. The raffles created by the batch continue through their own normal native raffle lifecycle.

Retry behavior

If one raffle creation does not finish successfully, Raffle Operations records the failed stage and can retry the operation instead of blindly creating another duplicate raffle.

Failure stages can include:

• access
• template validation
• raffle creation
• sync after create
• publish
• sync after publish

The retry flow is intended to continue or repair the failed raffle operation without making the manager recreate the whole setup.