IQ7 Game — From a selected action to a confirmed game entry

A selected control can still be a draft choice

An interface may highlight a choice before it is submitted. The highlight can help the reader see what is currently selected without proving that the service has accepted it. Read the surrounding labels and any remaining confirmation step. The visual appearance of a control is only one part of the interaction.

This matters when a page is slow or a countdown ends. A selected item can remain visible even though the relevant entry window has changed. The service's confirmation process determines whether the action belongs to that round. Do not use the persistence of a highlight as a substitute for the accepted-entry record.

Submission and acceptance answer different questions

Submission describes an attempt to send an action. Acceptance describes the service recording it under its rules. Between them, the interface may show a response, a rejection or an unresolved state. The exact sequence varies, so use the labels and history supplied by the selected service.

For a fictional example, a screen might show a request in progress and later show either a confirmed reference or an error. The initial progress message would not establish which final state occurred. The useful record is the eventual response or history entry, rather than a memory of having pressed the control.

Timing can be part of the acceptance rule

A live table or draw can limit when an action is accepted. An entry window closing is different from the game finishing. An action attempted near that boundary needs its own confirmation; the fact that a stream remains visible does not establish that entries are still open.

Connect the attempted action to the correct round or draw. If the interface has already advanced, a newly visible confirmation may relate to another item unless its reference establishes the link. The IO7 timing guide explains why deadlines and result publication should be treated as separate stages.

Use history after an uncertain interruption

When the connection returns, first identify the account and the relevant activity record. Determine whether the earlier action was accepted, rejected or remains unresolved under the service's labels. Starting another action before checking the record can add a second event without clarifying the first.

The absence of an immediate on-screen message is not proof of either acceptance or rejection. Retain the known time and the selected title or draw while locating the record. If no conclusive record is available, describe the status as unknown rather than assigning it a result based on the last visible animation.

Confirmation is not the final result

An accepted entry establishes that an action belongs to the relevant game or event. It does not establish the outcome. A later result stage resolves the entry under the applicable rules. Keeping these questions separate helps avoid treating an acceptance message as a success result or an unresolved outcome as a missing entry.

For a ticket, the accepted reference identifies the draw and selection to be evaluated. At a live table, the round identifier connects the action to the completed result. In a reel game, a feature may extend the sequence before the final record appears. Each format supplies its own completion process.

Report the exact stage that is unclear

A useful query says whether the uncertainty concerns selection, submission, acceptance or the final outcome. Include the available reference and the time of the interruption. If two screens disagree, quote their labels and identify which screen produced each one. That is more precise than saying an action disappeared.

The II7 history guide helps reconstruct the sequence, and the IT7 query guide explains how to present it. Do not send passwords or one-time codes with the record. The directory cannot resolve private IQ7 actions; the service's records are needed to establish what was accepted.

IQ7 confirmation questions

Does pressing a control prove an entry was accepted?

No. It establishes an attempted interaction. The service's confirmation or account history is needed to determine whether an accepted entry was created.

Should an accepted entry already have a result?

Not always. Acceptance and completion are different stages. A scheduled draw or ongoing round can have a recorded entry before its outcome is available.