I was testing what has changed after this was implemented, and I noticed that the list of background tasks defined in the dependencies often appears “late”.
- create a new app
M3 App 1
- add
ServerModule1
- define the background task
hello
- create a second app
M3 App 2
- add
M3_App_1
as a dependency - add the
Scheduled tasks
service - try to add a scheduled task → it says
You have no background tasks
- bad - refresh the browser and try again → it says
You have no background tasks
- bad - run and stop the app, and try again →
hello (M3_App_1.ServerModule1)
is listed - good - refresh the browser and try again → it says
You have no background tasks
- bad - click
Discard
to close the dialog and try again →hello (M3_App_1.ServerModule1)
is listed - good
I went through this testing because I was trying to reproduce the behavior of a production app that shows the same background task twice, but I wasn’t able: