I’m trying to use a Repeat step on a registration system, and I’ve found that the scope of the repeat is reset at every retry.
Here’s the scenario:
- A database stored procedure is called to register a client. If the username the client has chosen is not unique, a reponse is returned from the database which contains a choice of three alternative usernames.
- The repeat step begins: The first of these three usernames is chosen automatically and inserted into the original request.
- The stored procedure is called again. At this point, it is possible to return exactly the same error and a new choice of three usernames.
My problem is that the pipeline is reset at every repeat, which means that the choice of usernames is always the same.
Is it possible to preserve the pipeline between repeat steps?
If not, can anyone suggest an alternative approach to this scenario? I have toyed with the idea of a custom java service, but I may as well write the entire flow in java if that’s the only viable option.