Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I have a zap for each LearnWorlds account I am going to integrate with.   The first zap works perfectly.     The second zap is a carbon copy of the first zap.     When I’m updating the trigger of the second zap for the 2nd LearnWorlds account, it had the LearnWorks connection info from the 1st zap.   OK, probably doing this to help most people.    

However, when I change the 2nd zap trigger and select “+ Connect a new account”, it requests the LearnWorlds school id (good), but fails without asking for username and password (the error is “School not available to this user").   It seems like it is using username/password from the 1st zap trigger.

Any thoughts?

On this second zap trigger, want what to connect to a different LearnWorlds
After entering the second LearnWorlds School Id, normally I would have to enter a user and and ppassword.
But if fails without asking me for username and password.

 

Hi @QBankAdmin 

Try this tip:

 

Problem Solved.   I cleared browser cache and it worked.   I bet private or incognito work have worked as well.

That’s an awesome news @QBankAdmin! We’re glad to hear that clearing the browser’s cache solved the issue here.

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗

Reply


Terms & Conditions