---
title: "Offline Frontline Screens: What a Pass-Through Can Promise"
description: "What an employee pass-through can and cannot do when the warehouse network drops, including why balances cannot be cached."
url: https://kiweely.com/blog/offline-poor-connectivity-frontline-pass-through
---

# Offline Frontline Screens: What a Pass-Through Can Promise

Leaf reads Workday live and keeps no worker data after the request. A dropped network cannot show a stored balance or queue a submit. Workday Time Kiosk can record punches offline. That behavior is the kiosk’s, not the pass-through’s.

-   By Kiweely
-   November 16
-   2 min read

Frontline networks fail in walk-in freezers, yards, and basements. The honest question is which employee actions still work when they do. A pass-through that keeps no HR data has a short answer: actions that need Workday do not work offline, and they must not pretend to.

[Kiweely Leaf](https://kiweely.com/leaf) (coming next) is that pass-through. “Zero HR data at rest. Read on demand, gone when the request ends.” The phone app can be installed. The layout is configuration, not a cache of balances, payslips, or schedules. When the request cannot reach Workday, the screen has nothing true to show.

## What you can promise

The shell can open and say it cannot reach Workday. The worker retries when they have a signal. A submit that did not receive a Workday success is not submitted. Show that. A queue on the phone that sends the request later would hold the worker’s time-off dates or expense lines on the device, which is worker data at rest. The public design does not offer that queue.

You can promise that a published layout is what they will see once the network returns, because the layout is stored as configuration and the data is read again. You cannot promise that yesterday’s balance is still right. Accruals and approvals change on the server.

## What Workday already solved for punches

[Workday Time Kiosk](https://doc.workday.com/admin-guide/en-us/human-capital-management/time-tracking/time-entry-setup/time-kiosk/concept--time-kiosk.html) is built for a shared tablet that must record check-in and check-out during a local outage or Workday downtime. It stores locally encrypted employee data for 30 days. A worker can check in offline only if they checked in on that device while it was online within the previous 30 days. Data transmits when the app reconnects. Workday’s [Time Kiosk FAQ](https://doc.workday.com/admin-guide/en-us/human-capital-management/time-tracking/time-entry-setup/time-kiosk/faq--time-kiosk.html) says to expect 10 to 20 minutes after reconnect before offline punches appear in Workday. The kiosk is included with Time Tracking, it is a separate app from Workday mobile, and Workday does not recommend it on personal phones.

That is the offline promise for punches. It is not transferable to a Leaf payslip or time-off screen. Different app, different storage rules, shared device rather than a personal phone. If the floor loses network, punches belong on a kiosk that has been online in the last 30 days. Payslips and elections wait.

| Action | Offline |
| --- | --- |
| See a cached PTO balance in Leaf | No. Leaf does not keep the balance. |
| Submit time off later from a phone queue | No. That queue would store the request. |
| Check in on Workday Time Kiosk | Yes, within Workday’s 30-day device rule, then sync. |
| Trust a number painted from the last successful load | No. Show a failure until a live read succeeds. |

Poor connectivity is the same rule with more frustration. A timeout is a failed read. Retry. Do not fill the card with a stale figure and a small “as of yesterday” footnote. People will use the figure.

[Tell us the floor actions](https://kiweely.com/leaf) you need. If one of them is punch, say you already use Time Kiosk, and keep punch there.

## Read next

[All posts](https://kiweely.com/blog)

-   [November 16 ### Deep Links and QR Codes into the Right Employee App](https://kiweely.com/blog/deep-links-qr-codes-employee-workday-screens)
-   [November 16 ### HRBP Analytics Boards versus Chat Answers](https://kiweely.com/blog/hrbp-analytics-boards-versus-chat-answers)
-   [November 16 ### Versioning and Rollback for AI-Built Employee Screens](https://kiweely.com/blog/versioning-rollback-ai-built-employee-screens)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [How do I limit a Configuration Change Tracker package to a change window?](https://kiweely.com/guides/workday-configuration-change-tracker-time-bounded-packages)
-   [How do I build a Configuration Change Tracker package by user and time?](https://kiweely.com/guides/workday-configuration-change-tracker-how-to)
-   [Do You Need a Workday AMS Partner, or Can a Small In-House Team Run Workday?](https://kiweely.com/guides/workday-after-go-live-in-house-team)
-   [What Does a Workday Implementation Cost, and What Actually Drives It?](https://kiweely.com/guides/workday-implementation-cost)
-   [Set the Workday HCM foundation before you automate it](https://kiweely.com/guides/ai-workday-foundation-data-model)
-   [How Workday Data Conversion Works, and Why It Takes So Many Loads](https://kiweely.com/guides/ai-workday-data-conversion-mapping)
-   [Pre-Hire Windows That Create Directory Users Before Anyone Is Hired](https://kiweely.com/guides/pre-hire-windows-that-create-directory-users-early)
-   [Why Workday to Microsoft Entra Incremental Sync Misses Changes](https://kiweely.com/guides/why-workday-to-entra-incremental-sync-misses-changes)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
