Any caveats with changing Oban.Pro workflow step names after workflow is live?

Special Sections Oban
,
1

We have an Oban.Pro workflow live in production performing mission-critical work. I am working on expanding this workflow to handle more logic and my PR renames one step (ie: changes the first arg passed to the Workers.Workflow.add function):

     MyWorkflowJob.new_workflow()
-    |> MyWorkflowJob.add(:validate, validate_payment_step)
+    |> MyWorkflowJob.add(:validate_payment, validate_payment_step)

(where validate_payment_step is a job defined above)

Is there any concern with this change being rolled out to a live workflow? My guess/hope is that this “flow” param is metadata on the step and not dictating actual functionality but I’d like to be more sure of this before pushing to production.

2

Bleh, I don’t get this post syntax. The code example is intended to show a diff where the first line is unchanged and the second line is being replaced with the third line.

3

I changed the markup for you. It’s regular markdown, and you can use intended as well as fenced code blocks:

```diff
 Things
-WrongThings
+Right things
```

renders as

 Things
-WrongThings
+Right things
3 Likes
4

:+1: You can safely rename steps and the change won’t impact any existing workflows. The step name is injected into the job’s meta on workflow creation, and after that point it isn’t referenced at all.

1 Like