Correcting Completed Sessions

Fix a completed session's check-in or check-out time while preserving who changed it, why it changed, and the before/after values.

Availability and permission

Session correction is available on Premium, Pro, and Lifetime servers. The bot must be installed, and the person making the correction must be a server owner or Discord member with Manage Server or Administrator permission.

Free servers do not show correction controls. Sending a direct request does not bypass the paid feature or Discord permission checks.

Correct a session

Sign in to the Clocky dashboard with Discord.
Select a server you manage.
Open Check-ins.
Find a completed session and choose Edit.
Enter the corrected check-in and check-out times in your device's timezone.
Enter a clear correction reason and choose Save correction.

Corrected rows expose History, where managers can inspect each recorded change. There is no Discord member self-edit command.

Validation and conflicts

Clocky accepts corrections for completed sessions only. Both times are required, the check-out must be after the check-in, and neither may be in the future. The reason must contain 10–500 characters.

A corrected session is limited to 24 hours. If an existing exceptional record is already longer, a correction may not increase its duration. Every recorded break must remain fully inside the corrected time range.

If another manager changes the session after you open the dialog, Clocky rejects the stale save instead of overwriting the newer correction. Reload the session and review the latest values before trying again.

Correction history and privacy

Every successful correction creates a per-session history entry containing:

The previous and corrected timestamps and durations
The manager who made the correction
The required reason
The time the correction was saved

Only authorized managers of the same Discord server can view this history. It is not shown on public leaderboards or member-facing Discord commands. If the manager's dashboard account is later removed, the correction remains attributed to a former manager. Deleting the parent session through an authorized privacy/deletion workflow also removes its correction history.

Reporting history and downgrade behavior

The server's reporting-history window applies to the Check-ins list, CSV export, correction endpoint, and edit history. Records outside that query window cannot be corrected through the dashboard; the window is not an automatic storage-deletion schedule.

If paid access ends, correction controls and direct writes are disabled immediately. Existing correction history remains attached to its session and becomes available again if the feature is restored, unless an authorized deletion workflow removes the parent session.