-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure mid inport of 2085 note ENEX file #57
Comments
I can import this note just fine. |
That wasn't the whole note. When I pasted in the whole note Github said it was too big so I cut out a section in the middle.
On Friday, December 15, 2023 at 11:39:41 p.m. PST, Stefan Küng ***@***.***> wrote:
I can import this note just fine.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I am attaching the note in full in this email.
On Friday, December 15, 2023 at 11:39:41 p.m. PST, Stefan Küng ***@***.***> wrote:
I can import this note just fine.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
nothing attached here. Just zip it and attach it to the issue. |
I ran the import again with a new ENEX file. I selected only Create date, Updated date and Source URL attributes to export, not Tags. It ran a bit further before failing.
I have included the note zipped up so it should be smaller
On Friday, December 15, 2023 at 11:39:41 p.m. PST, Stefan Küng ***@***.***> wrote:
I can import this note just fine.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
again: nothing attached. |
Also: if this time it's not the same note, then the probability that your problem has anything to do with the note is basically zero. So attaching the note would not help. |
I agree. I don't think it is the note. Once it starts failing it fails on nearly all the proceeding notes. |
import went fine here. So problem is not the note. |
I am going to try again. My feeling is there are communication issues with OneNote. |
It failed again at the same note. I wonder if there is a API limit with OneNote.... |
Importing a ENEX file of 2085 notes. I get a failure at note 1214. After clicking OK on the error message nearly every note after that fails too, some with different exceptions. I can provide them if required.
One of the notes
<title>Blog.Amit Apple</title> 20140731T002215Z 20140731T002215ZThe text was updated successfully, but these errors were encountered: