Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Errors when starting process mining demo projects

Shane Baker
Tera Contributor

Hi Community!

 

I've just attended a session on Process Mining, where ServiceNow demonstrated the new free-tier demo process mining projects. 

 

I tried to run them myself, both on my base account with process mining roles and on my platform admin account. 

 

I'm not having any luck - it just gives me a generic error. Does anyone have any ideas?

13 REPLIES 13

Hi @Shane Baker 

Do you have admin rights in your instance? If not, assign them and try again.

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

Hey Atul! Yep, I am logged in as my admin account

Are you the creator of this project? Try copying this project and then perform the mining and testing.

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************

It seems like the instance does not have user with "admin" username.

The project is mined based on created_by field, in this case it is "admin" so, in order to fix the issue, you need to update the created_by field by using background script.