Why you can't edit a Timeclock record

If you open a VICIdial Timeclock record and find you cannot change it, or the Submit button refuses to work, there is a short list of reasons why. The Timeclock is the feature that tracks when each user is on and off the clock, and editing a record is gated by a few firm rules. Once you know them, every blocked edit has an obvious cause.

The login-plus-logout requirement

A Timeclock record can only be changed if it has both a login and a logout. A finished shift has both; an open one does not. This single rule is behind the most common complaint, which is the next reason on the list.

Reason one: the user is still clocked in

This is the number-one cause of a blocked edit. If the Agent is still logged in to the Timeclock, their active record has no logout yet, so it fails the login-plus-logout test and cannot be altered. The record is open-ended and the system will not let you touch it until the shift is closed.

The fix is to get them clocked out first. You can wait for them to clock out themselves, or force them out from the User Status page, which has the option to force a user in or out of the Timeclock. Once the record has a logout time, it becomes editable.

Reason two: the new times fail validation

Even on a closed record, the edit can be refused at the moment you try to save. When you change a Login or Logout time, VICIdial validates the new values, and if they do not pass, the Submit button stays disabled. Three things fail the check.

• A date that is not formatted properly. The system needs a real, well-formed date and time.
• A logout time before the login time. A shift cannot end before it begins.
• A logout more than 24 hours after the login. No Timeclock record may be longer than a day.

flowchart TD
  A[Try to edit record] --> B{Has login and logout?}
  B -- No, still clocked in --> C[Edit blocked: clock out first]
  B -- Yes --> D[Change Login or Logout time]
  D --> E{Times valid?}
  E -- Bad date format --> F[Submit blocked]
  E -- Logout before login --> F
  E -- Over 24 hours --> F
  E -- All valid --> G[Submit enabled]

The diagram is the whole decision. First the record must have both a login and a logout; if not, you clock the user out and try again. Then the new times must be a real date, in the right order, inside 24 hours. Pass all of that and the Submit button works. Fail any of it and the edit is held.

What is not the problem

It is worth ruling out a few things that look like edit problems but are not. The audit log, the immutable copy of what was originally recorded, genuinely cannot be edited by anyone, but that is by design and you are never meant to edit it; you edit the active log instead. The difference is explained in the Timeclock audit log. A record marked AUTOLOGOUT is fully editable, since the system already gave it a logout time; the star next to its ID just means it was force-logged-out, not that it is locked.

Once you have cleared the block, the actual editing steps are in how to edit Timeclock records. For how the whole Timeclock connects to the rest of the system, including each Agent session and the User Status (lead status) page, read the scheduled callbacks and timeclock guide. The same admin screens that gate these edits also handle held work like editing a scheduled callback.

If you would rather not manage any of this, VICIfast provisions a hardened VICIdial server with the Timeclock and admin tools ready in under 40 seconds. See our pricing for what each plan includes.