Create a User API call only sometimes works

[SamQuilter]

Hi All,

Just found that I every time I create a batch of new students, intermittently the Canvas call will fail to function.

Sometimes the problem is solved by running the UserCreation.ps1 script again and it just works sometimes.

Has anyone else had this intermittency with this?

Attached is the error in question and the code that is causing it, and the line in the code that is failing.

Thank you

Sam

[SamQuilter]

Update: I have also received this error trying to create the student manually:

[JamesSekcienski · Accepted solution]

@SamQuilter 

It looks like the error message from your script is saying that the password doesn't include symbols.  However, it doesn't look like you are setting a password when creating the user.  By any chance, do you have the new "Enhance password options" feature preview enabled with symbols required in the password?  We had enabled this setting and then received an SIS Import error when creating a user even though we don't include passwords as part of the user creation in our SIS Imports.  We had to disable the feature for now and are awaiting a resolution from Canvas Support on this issue.

For the error you received when in Canvas, it would be good to check the console log and/or network traffic using your browser's dev tools for any additional error messages.

[SamQuilter]

@JamesSekcienski 

Looks, like we do have it enabled, thanks James!

We'll trial it out, see how it goes, I'll update here if this is the solution that does the trick.

I am also awaiting Canvas Support's communication on a ticket we've made so hopefully this can be seen as something to look into for their (bug fixing?) team.

Did this only recently happen to your organisation as well?

[JamesSekcienski]

@SamQuilter 

You're welcome!  For us it happened with the first users SIS Import we had after the making the change in early October.  We disabled the change after this happened to avoid any further errors and haven't re-enabled it since we are still awaiting a solution on the support ticket.

[SamQuilter]

@JamesSekcienski 

Gotcha, my support ticket has now been responded to and they have confirmed that this feature is the issue. They are working on it. Until that fix is deployed, I'll mark your post as the solution as it absolutely helped!

Thank you