Common Issues and Solutions
Issue | Possible Cause | Solution |
Setup Fails | Invalid credentials or Timeclock ID | Verify credentials with supervisor. Confirm Timeclock ID from WebClock Setup. Check spelling of Company and Alias (case-sensitive). |
Employee Not Found (Online) | Employee not in database or inactive status | Contact supervisor. Employee may need to be added to system or assignment activated. Complete identification form after second PIN attempt. |
Employee Not Found (Offline) | Employee not in local cache | Device hasn't synced since employee was added. Complete identification form. When device comes online, data will sync. |
Offline for More Than 24 Hours | Extended network outage | Work Date Selector will appear when employee enters PIN. Select appropriate work date for current punch. Device will automatically sync all offline punches when connectivity restored. |
Sync Fail Errors | Data mismatch or validation failure | Check "Aqore Zen Time Sync Fail Report" in RMS. Review specific error message (PIN validation, multiple persons, multiple assignments). Correct underlying data issue in Zenople Web App. Manually attribute punches if needed. |
Geo-Fence Block | Employee outside authorized location | Move to authorized physical location and retry. Verify GPS is enabled on device. If strict mode causing issues, supervisor can change to warning mode in WebClock Setup. Check geo-fence radius configuration if too restrictive. |
IP Validation Failure | Device on unauthorized network | Connect to authorized Wi-Fi network. If using cellular, verify cellular IP is in allowed list. Contact IT if VPN required. Supervisor can temporarily disable IP validation if needed. |
GPS Not Working | Location services disabled or poor signal | Enable Location Services in device settings. Move to area with better GPS signal (outside, near windows). Restart device to reset GPS. If persistent, device may use last known location. |
Cannot Exit/Reset Device | Device offline or sync failure | Device must be online to exit/reset. Connect to Wi-Fi or cellular network. Verify internet connectivity. Force manual sync if needed. If sync fails, resolve sync issues before attempting reset. |
Punch Button Grayed Out | Invalid punch sequence | Check punch sequence logic. Example: Cannot Clock Out without Clock In. Cannot Break In without Break Out. Review left-side timesheet to see which punches already recorded. Contact supervisor if sequence appears correct but button still disabled. |
Assignment Picker Not Appearing | Only one active assignment | Assignment picker only displays when employee has 2+ active assignments for current work date. If you should have multiple assignments, verify with supervisor that all assignments are active and configured correctly. |
Updated Time Shows But I Didn't Change Anything | Automatic rounding or supervisor correction | Check with supervisor about organizational rounding policy. Supervisor may have made correction without notifying you. Review correction notes in Employee Portal if available. |
Break Compliance Survey Blocking Clock Out | Missed required break | Complete break compliance survey honestly. Explain reason for missed or short break. Contact supervisor if survey appears in error. Cannot bypass survey - it's required for regulatory compliance. |
Wrong Assignment Selected | Employee error during selection | Cannot change after punch recorded. Notify supervisor immediately. Supervisor will correct assignment attribution in web application. Be more careful on assignment selection in future. |
Device Running Slowly | Low storage or memory | Clear app cache (may require admin access). Restart device. Check storage space available. Export and archive old data if storage full. Contact IT for device maintenance. |
Clock Shows Wrong Time | Device clock not synced | Device clock should sync automatically. Check date/time settings in device OS. Ensure automatic date/time is enabled. Restart device. Punches use device clock, so correct time critical. |
Cannot See My Punches | Wrong work date selected or device not synced | Verify correct work date viewing. If offline, only local punches visible. If online, force manual sync by double-tapping displayed time. Check web application to verify punches were synced. |
Detailed Troubleshooting Scenarios
Scenario 1: Device Setup Fails with Authentication Error
Symptoms:
- Administrator enters credentials on setup screen
- Error message: "Authentication failed. Please verify credentials."
- Cannot proceed with setup
Step-by-Step Troubleshooting:
- Verify Credentials:
- Confirm username is spelled correctly
- Verify password (passwords are case-sensitive)
- Try logging into Zenople Web App with same credentials to confirm they work
- Verify Role Permissions:
- User must have Admin or Supervisor role
- Check role assignment in ATM → Role Navigation
- Verify user has access to the specific Timeclock ID being configured
- Verify Company and Alias:
- Company name must match exactly (case-sensitive)
- Alias must match exactly (case-sensitive)
- Small spelling differences will cause authentication failure
- Check Network Connectivity:
- Verify device has internet connection
- Test by opening web browser on device
- Check Wi-Fi signal strength or cellular data availability
- Contact IT/Support:
- If all above steps verified and still failing, credentials may be locked or expired
- IT administrator may need to reset password or unlock account
- Verify Timeclock ID exists and is properly configured in WebClock Setup
Scenario 2: Punches Not Appearing in Zenople Web App
Symptoms:
- Employee successfully punches on ZenTime tablet
- Punch confirmation displayed
- Supervisor cannot see punch in Zenople Web App timesheet
Step-by-Step Troubleshooting:
- Check Device Sync Status:
- On tablet, double-tap Company Name to reveal admin buttons
- Check "Last Sync" timestamp
- If last sync was before punch time, device may not have synced yet
- Wait for next automatic sync (within 10 minutes) or force manual sync
- Force Manual Sync:
- Double-tap displayed time on PIN Entry Screen
- Watch for sync confirmation or error message
- If sync fails, note error message for diagnosis
- Verify Device Online:
- Check for red offline indicator at bottom of screen
- If red, device is offline and punches stored locally
- Punches will sync automatically when device comes online
- Check Sync Fail Report:
- Log into Zenople Web App
- Navigate to RMS → "Aqore Zen Time Sync Fail Report"
- Search for employee name or date
- If punch appears in report, review error reason and correct underlying issue
- Verify Correct Timeclock:
- Confirm employee punched on correct timeclock device
- Verify timeclock is configured for employee's assignment
- Check if employee should have access to this specific timeclock
- Export and Review:
- Administrator can export punch data from tablet
- Review exported JSON file to verify punch was recorded locally
- If punch in export but not on server, indicates sync issue
Scenario 3: Employee Cannot Clock Out Due to Geo-Fence
Symptoms:
- Employee attempts to clock out
- Error message: "You are not within the authorized location."
- Punch blocked
Step-by-Step Troubleshooting:
- Verify Physical Location:
- Confirm employee is actually at job site (not clocking out from home)
- Ask employee to move closer to configured geo-fence center point
- Retry punch from different location within building
- Check GPS Status:
- Verify Location Services enabled on device
- Check GPS accuracy (device may display current accuracy)
- Poor GPS accuracy (>100 feet) may cause false negatives
- Move device near window or outside briefly to improve GPS signal
- Review Geo-Fence Configuration:
- Supervisor logs into Zenople Web App
- Navigate to WebClock Setup → Timeclock Properties → Geo-Location
- Verify geo-fence coordinates are correct for job site
- Check radius setting - may be too restrictive
- Example: 50-foot radius may be too small for large buildings
- Temporary Solution - Change to Warning Mode:
- If geo-fence blocking legitimate punches:
- Change enforcement from "Strict" to "Warning" mode temporarily
- Allows punch but flags for supervisor review
- Supervisor can approve after confirming legitimacy
- Later adjust geo-fence radius or coordinates to fix underlying issue
- If geo-fence blocking legitimate punches:
- Device-Specific GPS Issues:
- Some devices have poor GPS performance indoors
- May need to designate outdoor punch location
- Consider disabling GPS geo-fencing and using IP validation instead for indoor locations
Scenario 4: Offline Recovery Sync Takes Very Long Time
Symptoms:
- Device was offline for several days
- Device comes back online
- Recovery sync initiated but taking 20+ minutes
- Employees waiting to punch
Step-by-Step Troubleshooting:
- Understand Cause:
- Large volume of offline punches queued for upload
- Example: 50 employees × 4 punches/day × 3 days = 600 punch records
- Server processing each punch sequentially
- Network bandwidth may be limited
- Do Not Interrupt Sync:
- Allow sync to complete fully
- Interrupting sync (powering off device) may cause data corruption
- Employees can still punch during sync - new punches queued
- Monitor Progress:
- Some devices show sync progress indicator
- Check admin buttons for sync status
- Export data to verify punches still present locally
- Prevent Future Occurrences:
- Address underlying network reliability issues
- Consider backup internet connection (cellular failover)
- Perform daily data exports during known outages as backup
- Monitor network connectivity proactively
- Alternative - Staged Sync:
- If sync consistently failing or timing out:
- Export data from device
- Reset device to clear local cache
- Manually import exported data to Zenople Web App
- Reconfigure device with fresh setup
- If sync consistently failing or timing out:
Scenario 5: Identification Form Continuously Requested
Symptoms:
- Employee enters PIN multiple times
- Each time, identification form appears after second attempt
- Employee completes form but form appears again on next punch attempt
Step-by-Step Troubleshooting:
- Device Offline - Credential Mismatch:
- Most common cause: Employee entering slightly different information each time
- Example: "John" first time, "Jon" second time
- System treats as different people, creating multiple temporary records
- Solution: Employee must enter EXACT same information each time:
- Exact same spelling of first name
- Exact same spelling of last name
- Exact same last 4 SSN digits
- Online - No Matching Profile:
- Employee info doesn't match any profile in server database
- Check employee profile in Zenople Web App
- Verify spelling: "Robert" in system vs. "Bob" on form
- Verify SSN: Last 4 digits must match exactly
- Solution: Correct employee profile in web app OR instruct employee to use exact name/SSN as in system
- Multiple Employees Same Credentials:
- Duplicate employee profiles with same name and SSN
- System cannot determine which profile is correct
- Solution: Resolve duplicate profiles in Zenople Web App (merge or inactivate duplicates)
- Employee Not Assigned to Timeclock:
- Employee profile exists but has no active assignment for this timeclock
- Solution: Add assignment in Zenople Web App for employee's job with this timeclock ID
- Temporary Workaround:
- Supervisor manually enters punches for employee via web app
- Resolve underlying data issue during less busy time
- Train employee on proper form completion in the meantime
Advanced Troubleshooting - Device Logs
For persistent issues that cannot be resolved through standard troubleshooting, device logs provide detailed diagnostic information.
Accessing Device Logs
Android Devices:
- Connect device to computer via USB
- Enable File Transfer mode
- Navigate to Internal Storage → ZenTime → Logs folder
- Copy log files to computer for review
iOS Devices:
- Connect device to computer
- Open iTunes or Finder (macOS Catalina+)
- Select device → Files → ZenTime
- Save log files to computer
Log File Naming Convention:
- Format: ZenTime_Log_[Date]_[Time].txt
- Example: ZenTime_Log_2025-12-17_14-30-00.txt
- New log file created daily or when size limit reached
Log File Contents
Information Captured in Logs:
- App startup and shutdown events
- Sync attempts (successful and failed)
- Network connectivity status changes
- Authentication attempts
- Punch entries (with employee ID, timestamp, punch type)
- GPS coordinates for each punch (if geo-fencing enabled)
- Error messages and stack traces
- Database operations
- API request/response summaries (sensitive data redacted)
Example Log Entries:
2025-12-17 08:00:00 - INFO - App started
2025-12-17 08:00:15 - INFO - Loaded timeclock config: WH01
2025-12-17 08:05:23 - INFO - PIN entered: Employee ID 12345
2025-12-17 08:05:24 - INFO - Clock In punch recorded: 08:05:24
2025-12-17 08:05:25 - INFO - Sync initiated (automatic)
2025-12-17 08:05:28 - SUCCESS - Sync completed: 1 punch uploaded
2025-12-17 08:30:00 - ERROR - Sync failed: Network timeout
2025-12-17 08:30:00 - INFO - Will retry sync in 10 minutes
Using Logs for Troubleshooting
Common Log Analysis Patterns:
- Sync Failures:
- Search for "ERROR" or "Sync failed"
- Note timestamp and error message
- Common errors: "Network timeout", "Authentication failed", "Server unavailable"
- Employee Not Found:
- Search for employee ID or "PIN entered"
- Verify employee ID exists in local cache
- Check if employee data downloaded during last successful sync
- GPS Issues:
- Search for "GPS" or "Location"
- Check GPS accuracy readings
- Verify coordinates being compared to geo-fence
- Performance Issues:
- Look for slow database operations (queries taking >1 second)
- Check for memory warnings
- Identify any crashes or forced restarts
Sharing Logs with Support:
- Logs can be sent to support@aqore.com for advanced diagnostics
- Include description of issue and when it occurred
- Specify device model and OS version
- Support team can identify issues not visible to administrators