You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, if workflow try to upsert SA from within the workflow and it does not exists, the workflow task will fail and keep retrying forever.
Describe the solution you'd like
Give option for workflow to fail the command if SA does not exists
Describe alternatives you've considered
Work around is to use activity/localActivity to check if SA exists before call upsertSA.
But really the author should make sure the SA exists before the use case go online. Create SA should be handed as one time job and should not be created dynamicly. If you find that you need to create SA dynamicly, you probably doing it wrong. The number of SA is very limited.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Given that there's a workaround, we have put this on the backlog for now and will not get to it any time soon. Please bump this issue if you'd like to vote for it.
Is your feature request related to a problem? Please describe.
Currently, if workflow try to upsert SA from within the workflow and it does not exists, the workflow task will fail and keep retrying forever.
Describe the solution you'd like
Give option for workflow to fail the command if SA does not exists
Describe alternatives you've considered
Work around is to use activity/localActivity to check if SA exists before call upsertSA.
But really the author should make sure the SA exists before the use case go online. Create SA should be handed as one time job and should not be created dynamicly. If you find that you need to create SA dynamicly, you probably doing it wrong. The number of SA is very limited.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: