An invalid type conversion error occurs in Okta Workflows when a card receives an unexpected data type, preventing the flow from saving. Update the output data type to match the expected input type to resolve the error and save the flow. When attempting to save a flow with a data type mismatch, Okta Workflows displays red text on the affected card and generates the following error message:

Save Failure Your Flow cannot be saved because it is invalid. Correct the problems and try again.

Hovering over the red text on a card reveals further details, such as an invalid type conversion error. This occurs when an action or function card expects a specific type of input but receives a different type it cannot convert. For example, a List to Text card expects a list of text, but receives a list of objects.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Workflows

Okta Workflows validates cards when adding inputs and saving flows. If Okta Workflows detects a data type mismatch, it prevents saving the flow and generates an error.

How is the invalid type conversion error resolved?

Review the following examples of an invalid type conversion error and the difference between the two lists.

Update the output data type to match the expected input type to resolve the error and save the flow.

• 1. Locate the card displaying the red text.
  2. Verify the expected data type for the input field.
  3. Update the output data type of the preceding card to match the expected input type. Depending on the flow design, leverage other Function cards to achieve the desired format.
  4. Save the flow.

Related References

• Repair an invalid flow
• Send Mail Action for Office 365 Mail - Cannot Add Attachments - Error Received when Trying to Save the Flow