Cloudflare Developers•4w ago

Also I notice that the step name listed

Also I notice that the step name listed in the history have an int appended to them. Im not adding that so wondering why its there / where its documented

7 Replies

sdrOP•4w ago

const updatedRun = await step.do(`run.complete`, async () => {
...

const updatedRun = await step.do(`run.complete`, async () => {
...

sdrOP•4w ago

Isaac McFadyen•4w ago

Guessing that this is because a step will retry if it fails, and on successive retries the number will increase (-1, then -2, then -3, etc) Not 100% sure though, someone from the Workflows team would have to confirm for sure

sdrOP•4w ago

Yeah maybe its attempts. It would be strange to have a dynamic step name though

Craig•4w ago

Yeah because those names are dynamic and you can run in loops, it will increment each time it runs

Seekerdasbatatas•4w ago

yhep, the name can be duplicated in these cases so, for consistency, we add an integer to the end of each step name

itsmatteomanf•4w ago

it's not for retries, but yeah, if you do this you have a bunch of different steps with the same name

for (let i = 0; i < array.length; i++) {
    await step.do("handle array item", () => {})
}

for (let i = 0; i < array.length; i++) {
    await step.do("handle array item", () => {})
}

I don't like the integer at the end either, though :NotLikeThis:

Gaming

Programming

Also I notice that the step name listed