You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an integration test for the path where an in-flight Redis job
enqueued by the old engine (no `lastScheduleTime` in its payload) is
dequeued by the new engine. The new engine must report the value
persisted at `instance.lastScheduledTimestamp` as `payload.lastTimestamp`
rather than reporting `undefined`, so customers don't see a one-fire
gap in their lastTimestamp during the rollout.
The existing integration test exercises the fresh-schedule path and
the worker payload flow on subsequent fires. This new test
specifically exercises the DB-column fallback in the
`params.lastScheduleTime ?? instance.lastScheduledTimestamp ??
undefined` chain — the bridge that handles the legacy queue at
deploy time.
0 commit comments