Persistent Error
reidpat opened this issue · 10 comments
Getting an error whenever I try to use the plugin:
"Error processing webhook events, Error: ENOENT: no such file or directory, mkdir 'C:\Obsidian Notes\REDACTED'
I did make a mistake in my request and put in a non existent folder. But now nothing will run and no matter what URL I post to it will only come back with this error.
Tried clearing buffer, uninstalling plugin, clearing cache, restarting obsidian, restarting computer. Nothing worked
This is happening for me too. Any updates on this?
Same issue for me. Tried creating a brand new vault, reinstalling the plugin, clearing the buffer on the website, etc. None work. Same error. The problem persisted even when I make a POST request with a different folder.
Im struggling to reproduce this. Would you be able to show me whats in your developer tools console?
On Mac its: View menu, Toggle Developer Tools? Im looking for lines that look like this
I sent a request from postman to the following URL: https://us-central1-obsidian-buffer.cloudfunctions.net/webhook/.....?path=Captures/Emails.md
But it throws an error. Here is the screenshot of the developer console:
Also mentioning the fact that this error started occurring after I set up an automated webhook event (I don't remember well, but it was on either IFTTT or Make).
You know every person Ive seen this happen to has had a windows account! Im developing this on a mac, I wonder if thats part of the puzzle
Okay Ive had some time to work on this.
- The clear buffer button was not doing what it needed to do to put accounts into healthy states. so if you had a message you couldnt process you would never be able to to get out of the bad state. So please try and press the clear buffer button once again.
- Ive added a bunch more logging on the server to look for issues. Let me know if you hit something and I will have more data to debug this now.
Sorry for this late reply, Mac user here :) and I am using Shortcuts to submit the POST request and here is the error in the developer console:
Woohoo!!! Clear the buffer again this morning, and the error is gone and it works now!!! Thanks @trashhalo. Much appreciated. Very happy.
For me too!!! Happy start for the day