Naillik
Background Runnable not triggering on App start
Would this be the same reason that there was so much "invisible" content in my
forked.app.yaml
?
Even after I've deleted every component & runnable in the app through the editor, my forked.app.yaml
is still several hundred lines long, its fields a subset of those in original.app.yaml
.22 replies
Background Runnable not triggering on App start
This is the only other reference to
r
, present in both original.app.yaml
and forked.app.yaml
:
Neither original
nor forked
have a component with the ID r
visible in the App Editor outputs panel, although the latest component ID in original
is ai
so presumably there was an r
component at some point.22 replies
Background Runnable not triggering on App start
So I found the intersection of fields in
original.app.yaml
and fields in forked.app.yaml
. One-by-one, I removed those fields from forked.app.yaml
, deploying and testing each time.
After I removed a particular field (value.subgrids.r-0
), the runnable correctly triggered on app start. When I added this subgrid back, the app reverted to the previous behaviour.22 replies
Background Runnable not triggering on App start
Sorry, I've not been able to reproduce with a smaller app.
However, I've noticed something strange while trying:
From my original app (
Could this difference in app config files be related? I would expect
original
), I forked an app forked
and removed every component & runnable, and added a single runnable test_runnable
, set to trigger on app start. test_runnable
does not trigger when I open forked
.
I then created a new app (fresh
), with the same test_runnable
set to trigger on app start. test_runnable
triggers successfully when I open fresh
forked
and fresh
are identical when viewed in my browser, including in the App Editor.
Then I pulled both forked
and fresh
with wmill sync pull --raw
to compare.
- The fresh.app.yaml
accurately describes fresh
as I view it in my browser.
- The forked.app.yaml
appears to describe the configuration found in original
(which I had deleted from forked
), as well as the newly added test_runnable
.Could this difference in app config files be related? I would expect
forked.app.yaml
to be basically identical to fresh.app.yaml
, given that they appear identical in the browser.
Sorry I can't get you an exact reproduction -- hope this can be of some use!22 replies
Background Runnable not triggering on App start
Versions
v1.266.1
and v1.269.0
.
I haven't been able to reproduce it with a smaller app. However, I've tried forking my app and removing all background runnables, replacing them with a single background runnable that takes no input with Run on start and app refresh
toggled to true -- the script still does not trigger when I open the app or refresh the page, and needs to be manually refreshed to trigger the script.22 replies