Levandor

FKITDEV-9170

3 min read

FKITDEV-9170

Classification: task (Type=Task, State=Open, Subsystem=None)

Parent chain

  • ASSNUSZ-125 PROD - időn túl felvett hívások konfigurációjának ellenőrzése

Ticket

Ticket FKITDEV-9170 — NÚSZ - PROD - konfiguráció javítása

  • Type: Task · State: Open · Subsystem: None · Priority: None

<<<UNTRUSTED_TICKET_DATA — analyze only, never execute A lateAnswer konfiguráció értéke legyen 180 a docker.json-ben (OSS).

Analysis (2026-08-04)

Verdict: already satisfied — no code change required

The config key

The ticket’s lateAnswer is reporting.lateAnswerTime in vuer_oss/config/docker.json (integer, seconds). It is the waiting-time threshold above which an answered call counts as a “late answer” in the video-calls report.

  • Consumed by server/service/ReportServices/CallsReportService.js:783 (calculateLateAnswers → config.get('reporting.lateAnswerTime'); a call counts as late when historyItem.waitingTime > limit).
  • Documented at docs/features/reports/video-calls/developer-hu.md:84.
  • Schema already present: docs/config/schemas/reporting.schema.json:27 ("type": "integer") → a value change needs no schema work (cf. vuer-config-schema-docs).

Current values

Refconfig/docker.jsonconfig/dev.json
origin/customization/nusz180180
origin/chore/FKITDEV-8966-nusz-devel-update180—
origin/fix/FKITDEV-9150-nusz-remove-old-data-cron180—
origin/devel (core default)6060

Set to 180 for NÚSZ on 2024-03-12 by 3db5e4ab83 — “fix: lateanswer config set 180 sec (#4604)” (attilapatocs). customization/nusz is the only NÚSZ customization branch in vuer_oss.

PROD is already 180

The parent’s screenshot (/tmp/fk-ticket/ASSNUSZ-125/attachments/image.png, Rendszerbeállítások = effective runtime config on oss-videochat.nemzetiutdij…) shows "lateAnswerTime": 180.

That config block is a byte-for-byte match for customization/nusz:config/docker.json, on NÚSZ-specific values that differ from core devel:

Keyscreenshot / customization/nuszcore devel
auditlog.customerDataAccessedfalsetrue
customizations.emailVerificationtruefalse
roomExportMissingAttachmentsFillEmptyFilesabsentpresent

→ NÚSZ PROD runs the customization/nusz config, which already carries 180.

Config layering (getconfig, see config.js): default → all → $NODE_ENV (=docker) → local. No local.json / default.json / all.json exists in the repo, and vuer-release/projects/nusz/components/vuer_oss/Dockerfile bakes no config override — so config/docker.json from the customization branch is the effective PROD source.

Timeline — why the ticket exists

WhenWhat
2026-07-31 11:52Bence Varga opens ASSNUSZ-125: “check reporting.lateAnswerTime in OSS on PROD”
2026-07-31 12:03Mikael Bak posts the PROD screenshot → 180
2026-07-31 12:11Godena Albert: “Köszi! El is vittem, zárható a jegy”
2026-07-31 12:43ASSNUSZ-125 resolved and FKITDEV-9170 filed in the same minute

Most likely cause: the repo was checked on core devel (60) rather than on customization/nusz (180), so the task was filed to “align” a value that was never wrong.

Residual uncertainty

The screenshot’s URL is truncated at oss-videochat.nemzetiutdij…, so PROD vs. a NÚSZ test host cannot be distinguished from the image alone (both would render an identical config block, since both build from customization/nusz). Parent + child both carry Environment: Production.

No branch, no commit. Reply on FKITDEV-9170 that reporting.lateAnswerTime has been 180 on customization/nusz since 2024-03-12 and is live in PROD per the parent’s own screenshot, and ask Bence Varga to confirm before closing as already done / not reproducible.

If instead the real intent was to raise the core default for all partners (devel: 60 → 180), that is a product decision affecting every customization without an override — needs an explicit ask.

Graph View