wemakefuture

Results 10 comments of wemakefuture

@CLAassistant singed it

> [![CLA assistant check](https://camo.githubusercontent.com/4c970efeed75dd01f6778bf7e33dec85e4171375cb69acb0927bfc9d437d78d9/68747470733a2f2f636c612d617373697374616e742e696f2f70756c6c2f62616467652f6e6f745f7369676e6564)](https://cla-assistant.io/n8n-io/n8n?pullRequest=3233) Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our [Contributor License Agreement](https://cla-assistant.io/n8n-io/n8n?pullRequest=3233) before we...

![image](https://user-images.githubusercontent.com/28114725/167676065-87430e5a-9701-47c5-9424-39b00196e306.png) We had this in the past, the account was created via SSO and was later switched to Email based and the email was changed several times. This conflicts usually...

@Joffcom that might be for bigger customers a nightmere if a developer pushes with its account and you now need to add the developer on the main account - securitywise...

@Joffcom can you please update us on the status?

Yes it broke. Error message is "login failed, Cookie not found"

@RienNeVaPlus yeah - the old layout was smooth. Getting the trades is currently not working, patched 0.4.2. Trying to grab the trades ends with a: `[-] No trades found.`

today this occurred at my vps too. ` Failed getting oauth client: Failed to read token: invalid character '}' after top-level value `

I reinstalled it and it fixed it. My problem.was that after a half year the free version of gdrive (private user) needs a new auth code...I tried for 2 hours...

@felipeelia would be great to have this feature. It still bugs.