Destination status could not be resolved error is shown - but Status gets updated

[Ramya Srinivas]

I get the below Error but the Status does get updated correctly when creating a sub-task.

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):

[John Funk]

Hi Ramya,

I suspect it is just a timing thing or maybe that there is something else that still triggers it. You might want to put a Re-fetch action prior to the action to transition so it has time to process what is going on.