Why Does PD Think the Results Are Out of Date Immediately After a Test in Newly Built Workflow Using a CRON Trigger and Code Step?

1

This topic was automatically generated from Slack. You can find the original thread here.

May be a bug, but figured I’d ask here. I built a new workflow using a CRON trigger and a code step. super simple. now, every time i run the code step i get a warning (possibly out of date). why does PD think the results are out of date immediately after a test?

2

I can’t reproduce that — can you show a screenshot or screencast?

3

sorry for the size -

4

image.png
image.png1698×1271 200 KB

5

And that’s immediately after testing, without making any changes?

6

yep

7

oh, also - ive got 2 warnings for thisd workflow - trigger not tested, code not tested. ive run tests multiple times

8

Ah yes, okay I can repro in a git-backed workflow. Thanks for flagging! Looking into it.

9

cool beans

10

FYI this is fixed — you might need to refresh the page to get it.

11

45 minutes to fix a UI bug - can’t yall work quicker :stuck_out_tongue:

12

confirmed - thank you

13

:pray::skin-tone-2: :pipe: