Error message “This status is not in an authorized sequence.”

[sync-by-unito]

┆Issue is synchronized with this Monday item by Unito

[sync-by-unito]

➤ sheri_jennings@tsco.org commented:

@Cathy Wang ( https://seed-company-squad.monday.com/users/42268518-cathy-wang )  can you assign a dev so this can be added to grooming. Dev would need to identify what needs to be done. @andre Turner ( https://seed-company-squad.monday.com/users/37419707-andre-turner )  did you already do some investigation on this ticket?

[sync-by-unito]

➤ Renato Rossiter commented:

Adding another Halp ticket:

https://seedcompany.halp.com/tickets/10447 ( https://seedcompany.halp.com/tickets/10447 )

[sync-by-unito]

➤ sheri_jennings@tsco.org commented:

Next steps- Need developer to dig into code and identify what conditions are causing this error or need to be changed.
Also, review error message content and change to clear message as to why they are receiving the error.

[sync-by-unito]

➤ Renato Rossiter commented:

Adding another Halp ticket (this one also involved multiple projects):



https://seedcompany.halp.com/tickets/10549 ( https://seedcompany.halp.com/tickets/10549 )

[sync-by-unito]

➤ Renato Rossiter commented:

Another Halp ticket: https://seedcompany.halp.com/tickets/10318 ( https://seedcompany.halp.com/tickets/10318 )



The FPM/RD experienced the issue on multiple projects.

[sync-by-unito]

➤ Renato Rossiter commented:

I have found 24 Halp tickets related to this issue. The first ticket is from July 2021. This year, I got at least 14. Here are some of the most recent ones:



1: https://seedcompany.halp.com/tickets/10276?message=65527cd886ec77d61cbd535a ( https://seedcompany.halp.com/tickets/10276?message=65527cd886ec77d61cbd535a )

2. https://seedcompany.halp.com/tickets/10209 ( https://seedcompany.halp.com/tickets/10209 )

3: https://seedcompany.halp.com/tickets/10166?message=6537d4514e080f6055602b28 ( https://seedcompany.halp.com/tickets/10166?message=6537d4514e080f6055602b28 )

4: https://seedcompany.halp.com/tickets/10059?message=651ebbb00724d396a878ca44 ( https://seedcompany.halp.com/tickets/10059?message=651ebbb00724d396a878ca44 )

5: https://seedcompany.halp.com/tickets/9753?message=65030b9c08e7920547981693 ( https://seedcompany.halp.com/tickets/9753?message=65030b9c08e7920547981693 )

6: https://seedcompany.halp.com/tickets/9693?message=64d6639754030f4236026181 ( https://seedcompany.halp.com/tickets/9693?message=64d6639754030f4236026181 )

[sync-by-unito]

➤ Seth McKnight commented:

Investigate why users sometimes receive an error that a status is not authorized when a user goes through valid workflow steps.

Issue: Error message "This status is not in an authorized sequence."

@renato Rossiter ( https://seed-company-squad.monday.com/users/42248649-renato-rossiter ) used one of the internship projects in dev with a single engagement. To conduct the test, I impersonated the FPM within the project. I completed all the standard developmental steps, and once the project was approved, it moved to the "Active" stage. The engagement status was then updated to "Active."
Based on recent Halp tickets, I conducted tests in the folding scenarios:

1. Update the engagement from Active to Discussing Change to Plan first, then change the project status from Active to Discussing Change to Plan: I was not able to change the project status and received the error message.
2. Update the project status from Active to Discussing Change to Plan without changing the engagement status first: I had no issues updating the project status; the engagement status followed the project.
3. Update the project to any step, switch back to Active (by selecting Will Not Change Plan, Will Not Terminate, Still Working, etc.). and then try to update the project status again: the engagement status did not change back to Active: I received the error message.
4. Update the project to any step, switch it back to Active, move the engagement back to Active individually before updating the project (by selecting Still working. Will Not Change Plan, etc.), and then try to change the Project: I was able to update the project status; the engagement status followed the project's.

[sync-by-unito]

➤ Cathy Wang commented:

The description of this issue is at the Files tab.