ACME HQDemo work items and pages, made up for Emargen's demo. Not a real company.
Engineering / ENG-1232

ExpireRequests closed 14 requests after 13 days

Project
Engineering
Type
Bug
Status
Done Done
Priority
High
Reporter
Marek Nowak <marek.nowak@acme-hq.example>
Assignee
Marek Nowak <marek.nowak@acme-hq.example>
Labels
None
Components
identity-service
Fix versions
identity-service 2025.12.03
Sprint
Sprint 30
Created
1 Dec 2025, 09:25 UTC
Updated
3 Dec 2025, 14:10 UTC
Resolved
3 Dec 2025, 14:10 UTC

Description

After the scheduler moved to the new worker host on Sunday, identity-service:src/Jobs/ExpireRequests.php ran at 01:00 local time and compared created_at (UTC) with a cut-off date built from local time. Requests made on the evening of 17 November were closed on 30 November instead of 1 December.

Steps to reproduce

  1. App time zone Europe/Berlin, host in UTC.
  2. Create a request at 23:30 local.
  3. Run ExpireRequests 13 days later at 01:00 local.

Expected: request stays waiting. Actual: request is closed.

14 requests at 4 clients affected. Nobody is told when a request expires, so no customer noticed; we reopened them. See OPS-23.

Linked issues

Comments (2)

Marek Nowak · 1 Dec 2025, 14:40 UTC

Fix: cut-off built in UTC, plus a test pinned to a host in UTC. The 14 requests are back to waiting with their original dates; list in OPS-23.

Rafael Duarte · 2 Dec 2025, 08:05 UTC

OK. Worth noting somewhere that expiry tells nobody. Not for now.