magento2: Error when updating category scheduled changes for a specific store view
Preconditions and environment
- Magento version: 2.4.5-p1
- PHP 8.1
- Setup with at least 2 store views
Steps to reproduce
- Navigate to Catalog > Categories in the admin section
- Change the scope to a specific store view
- Select any category
- Create a new scheduled change for the category for the specific store view
- Save the schedule and the category
- Update the existing schedule, change the end date of the existing schedule and try to save it
Expected result
The schedule is saved.
Actual result
The following error occurs:

Additional information
I was able to reproduce this issue on a clean 2.4.5-p1 installation with sample data.
The following log regarding the issue can be found in system.log:
[2023-03-14T20:52:30.453553+00:00] report.CRITICAL: Exception message: Warning: Undefined array key "updated_in" in /app/vendor/magento/module-staging/Model/Operation/Update.php on line 174
Release note
No response
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 29 (1 by maintainers)
Hi @GioDeGruyter ,
Issue confirmed !
Verified the issue in 2.4-develop instance and the issue is reproducible,Hence we are confirming the issue.
Preconditions:
Magento Version 2.4-develop PHP Version 8.1 Multi store was created
Steps to reproduce:
Kindly Refer the below screenshots:

We are trying to Update the existing schedule(change the end date of the existing schedule and try to save it),But we getting the error which is attached in above screenshot also we are getting same system.log as per the description and system.log screenshots also attached.This is actual result,So we are confirming the issue in 2.4-develop instance.
Regards,