Health and morning check

The Health tab

Open the FrontTailor panel in DevTools (F12) or the side panel and choose Health. The status bar at the top is computed from the recording of the OData console: it sends no request of its own but evaluates what the app talks to its backend anyway. In the side panel it is compact.

1. Backend latency: median and p95 of the last 50 completed requests.
2. Error rate: share of responses with status 400 or above, status 0 or network errors – including single parts of a $batch.
3. Session: estimated time left or last activity … ago.
4. Login & CSRF: 401 and 403 of the last two minutes and rejected CSRF tokens.
5. Show request jumps to the OData console and selects the failed request.

Replays from the OData console do not count. If OData recording is off for the host (policy or your own choice), the tab says so instead of showing empty values.

Session and tokens

The browser does not know when the server session expires: the cookie is HttpOnly, and FrontTailor reads no cookies. The Session & tokens card therefore estimates:

• the timeout from the launchpad configuration (the same setting the launchpad uses for its own sign-out dialog) – with reminder and automatic sign-out, if set;
• the starting point from the last successful backend request;
• a new backend session when sap-contextid changes between two requests.

The remaining time is marked as an estimate; ICF, approuter or identity provider may have their own timeouts. Without a launchpad it only says “No launchpad: the session timeout is not visible in the browser.” If the ABAP add-on is installed (backend service), the timeout comes from the system instead of the launchpad. A rejected CSRF token (403 with x-csrf-token: Required) is reported explicitly: session or token expired, the app must fetch a new token.

Synthetic check

Record a click sequence once and replay it when needed – for example after a deployment, to compare load times. The recorder bar is the same as in the Report a problem and Scaffolding tabs; all three see the same recording.

1. Click Record in the recorder bar. The bar counts steps and time (at most 200 steps and 10 minutes).
2. Click through the flow in the app. Only real user clicks count; typed text is only recorded if you tick Record typed text (masked).
3. Click Stop. The Synthetic check card lists the steps.
4. Choose the Timeout per step (5, 10 or 30 s) and click Run check.

1. The steps with status, wait until the control appears, load time and number of requests.
2. The result: Check passed in … or Check failed after ….
3. Run check replays the sequence in the current tab, starting at the same location hash.

For each step the check finds the control, clicks it and waits until the page has been quiet for 500 ms. If it cannot find a control (Control not found) or time runs out (Timeout), it skips the remaining steps. Generated ids like __button3 often differ after a reload; the tab marks such steps with generated id.

The morning check

Instead of opening ten apps by hand every morning: a check list opens them one after another in a background tab, waits until each one is quiet and closes it again. Nothing runs before you click.

1. Choose the Morning check tab and click Create list – or Start with this app, then the current app is already in it.
2. Add apps: a URL or a launchpad intent such as SalesOrder-display. For intents the list needs the Launchpad URL. Add current app takes over the tab’s page.
3. Save, then Start check. In the same click, FrontTailor asks once per system for access; apps of systems without access stay grey.
4. The report fills app by app. Stop ends the run after the current app.

1. Launchpad URL (for intents) – the check opens every intent of the list there.
2. Open apps in: background tab or own window. Browsers slow down timers in background tabs; an own window measures closer to a real start. Only compare runs of the same mode.
3. The list’s apps, up to 30, each with name, target and optionally the steps of a saved recording.
4. Add current app. FrontTailor removes session-bound parameters such as sap-iapp-state, and user and password in URLs when saving.

Report and traffic light

1. Run: choice of earlier runs with their balance (green, yellow, red).
2. A red app with its reason – here HTTP 404. Details expands failed requests and UI5 log errors, Open app opens it.
3. The comparison with the last run of the same list, for example today 2.1 s, now 679 ms – two runs on the same day are compared as “today” and “now”.
4. Export: Copy as Markdown, To issue reporter and files as Markdown, CSV and HTML.

In the comparison the report counts failed requests as new or fixed. FrontTailor masks exports with the PII rules of the issue reporter; To issue reporter opens the Report a problem tab with title and description, and nothing is sent before preview and click.

Daily reminder

In the Daily reminder card, switch on Remind me every day, choose the time (05:00 to 12:00 in quarter hours) and, if you like, Monday to Friday only. At that time a sun ☀ appears on the FrontTailor icon and a note in the tab. The check does not start by itself and nothing is sent; the sun disappears with the next run.

Check lists can be shared in the team via Team sync; they then carry the Team tag. Runs are not shared. Lists and the last seven runs per list stay in the browser, request addresses without query strings.

Typical problems