Known limitations when using Workflow Studio
When working with Workflow Studio, there are several limitations that you should be aware of.
Workflow Studio does not support dynamic resource IDs
You cannot use dynamic ARNs in the Resource
section of a Task state. Instead, you can enter the
dynamic ARN in the appropriate Parameters
field of your task state. For
example, if you have the dynamic ARN ${my-input}
, you could add to the
field as seen in the following:

State machine definitions that contain Amazon CloudFormation references cannot be saved. However, you can copy or export the definition for use elsewhere.
Workflow Studio does not automatically save workflows
Currently, Workflow Studio doesn't automatically save your workflows. In case of an Amazon console timeout, you could lose your work. Therefore, we recommend that you save your workflows or export their Amazon States Language definition frequently.
On the console, you can save a workflow after creating it or save the updates made to an existing workflow on its edit page. In either scenarios, your state machine definition must be valid to save it.
For information about console session expiry, see Amazon Web Services Management Console FAQs
Workflow Studio does not support Internet Explorer 11
Internet Explorer 11 is not supported by Workflow Studio. If you are you using Internet Explorer 11 and encounter issues using Workflow Studio, try using a different browser.