It's saying there was a timeout of the global scheduled action but it seems to be running fine
It also keeps retrying it
Trace ID: dd18f7a18cafaee46ac71c76db4cd67a
Example trace ID of the thing that the scheduled action causes to run:
a9cb0b34ba06e565f2b729c252a60e34
3 Replies
Here's a clearer example of a trace:
dd18f7a18cafaee46ac71c76db4cd67a
You can see that it timeouts but then it keeps going and finishes executing.
I did just go ahead and set timeoutMS to 5 minutes on this one so maybe that will help but I'd still like to understand why it happened like this when timeoutMS wasn't set.
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
nailed it - I think I found them
damn you're good 🙂