<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009nGv5FCASOkta Classic EngineMulti-Factor AuthenticationAnswered2024-04-03T16:09:08.000Z2023-10-27T04:17:56.000Z2023-10-31T22:40:57.000Z
Getting 204 error while executing work flow This work flow is for MFA trigger policy

If user give 2 unsuccessful password attempts MFA need to trigger for this we have created work flow while executing i am getting 204 error

 

Error : Invalid type conversion: Cannot parse string invalid number at line 1 column 2


  • MatthewH.10249 (State of Iowa)

    I think we would need to see the exact Workflow card along with inputs and outputs in order to give any suggestions. Rather than updating this post, I suggest you attend an Okta Workflows Office Hours online meetup that are held multiple times each week. This will give you an opportunity to share your screen and use case with Workflows experts who should be able to quickly tell you what is going on.

     

    Okta Community Hours: "Live answers to builder questions from Workflows advocates in a semi-private group"

    (Link bottom right) https://support.okta.com/help/s/product-hub/workflows/builder-community?language=en_US

    (Link to sign up) https://calendly.com/oktaworkflows

     

    If you don't wish to attend a Workflows Office Hours event, I again think you will need to provide more details in order for the community to respond with anything useful. It will be important to know if this a 204 HTTP code which would mean success or a E0000204 which would mean "SMS rate limit exception 429". Also knowing what Workflow action card is failing and what its exact input and output values would be a must to know.

     

    Okta error code info: https://developer.okta.com/docs/reference/error-codes/#E0000202

    Okta SMS rate limits: https://developer.okta.com/docs/reference/rl-additional-limits/#sms-and-call-rate-limits

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    Quick add:

     

    >Error : Invalid type conversion: Cannot parse string invalid number at line 1 column 2

     

    This typically means a value being passed into a field is not the expected type. So for example:

     

    • If a number (integer) is expected and an alpha (string) character is provided.
    • If an object is expected and a list is provided.

     

    And so on.

     

    Usually you want to look at the card(s) that are the source(s) feeding data into the card that is generating an error.

    Expand Post
This question is closed.
Loading
Getting 204 error while executing work flow This work flow is for MFA trigger policy