In rules, context.connection sometimes `undefined` during token refresh

During token refresh we’ve started seeing context.connection being undefined in our rules. This is only happening for username-password connections and it isn’t happening 100% of the time. We also have a couple of custom social connections that still seem to be working consistently. We’ve been using the connection from the context to select the corresponding identity in our linked accounts, so this is breaking our refresh flow. The only recent change we made to our configuration was renaming an application.

Should the context object of token refresh always know the connection type?

Hey there!

As this topic is related to Rules - Hooks - Actions and Rules & Hooks are being deprecated soon I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!

Learn more here!