docs: fix step name in long-running workflow documentation (#12215)

* docs: fix step name in long-running workflow documentation

Fixed inconsistency in the step name - updated 'set-step-failure-step' to 'setStepFailureStep' to match the exported function name.

Fixes #12143

* docs: fix step name in long-running workflow documentation

Changed the step ID from "setStepFailureStep" to "set-step-failure-step" as requested to follow kebab-case naming convention for step IDs.

Fixes #12143

* Update page.mdx

I think this is done. Sorry for inconvenience caused by me.

* Update page.mdx

Sorry for the inconvenience.

* Update page.mdx

Sorry for the inconvenience.

* Update page.mdx

---------

Co-authored-by: Your Name <your-email@example.com>
This commit is contained in:
Vallabh-Mahanta
2025-04-17 21:38:52 +05:30
committed by GitHub
parent 8b5b96a83d
commit 6a9417a1bb

View File

@@ -252,7 +252,7 @@ type SetStepFailureStepInput = {
};
export const setStepFailureStep = createStep(
"set-step-success-step",
"set-step-failure-step",
async function (
{ transactionId }: SetStepFailureStepInput,
{ container }
@@ -391,4 +391,4 @@ However, instead of the `subscriber` property, it requires a `subscriberOrId` pr
To find a full example of a long-running workflow, refer to the [restaurant-delivery recipe](!resources!/recipes/marketplace/examples/restaurant-delivery).
In the recipe, you use a long-running workflow that moves an order from placed to completed. The workflow waits for the restaurant to accept the order, the driver to pick up the order, and other external actions.
In the recipe, you use a long-running workflow that moves an order from placed to completed. The workflow waits for the restaurant to accept the order, the driver to pick up the order, and other external actions.