A
The destination execution context for this RPC was canceled while the call was still running.
Z
W
S
DD
wrangler workflows instances describe
MM
D
D
D
D
OOO
M
S
A
AAAOD
await step.sleep('wait on something', '1 second') but here it says the wall time for this step is 254ms .. any idea why it's lower than what the wall time should be?
D
Dwait on something (Sleep)D
ASerialized RPC arguments or return values are limited to 1MiB which I think happens when the returned values of a step are larger than 1MiB.ASAS
F
,
Trigger Button to trigger a workflow, the Params are submitted with some extra characters 
1
JSON.parse() on the params first1Trigger button doing the stringify, or if wrangler not stringifying would count as a bug hereF
for the feedback. I think for the button you can only enter „valid json“ so a stringified version is not validated in the modal text input. But yeah you are right if i input a non stringified json, after clicking trigger it gets stringified which makes my workflow fail. 
L
S
S
DDS
FFFDFFFF
await step.sleep('wait on something', '1 second')254mswait on something (Sleep)Serialized RPC arguments or return values are limited to 1MiBTriggerTriggerParamsnpx wrangler workflows trigger create-campaign-from-url-workflow --params='{"url":"https://www.backlinkgpt.com"}'JSON.parse()ctx.serviceSendClient(MyService).myHandler(payload, { delay: 5000 });