OneNote - issue after sign in with version 1.6.1

[fjacquet]

OneNote - issue after sign in with version 1.6.1

[enoola]

Hello I experiment the same with macbook m3 (16-inch, Nov 2023) , I have HAR capture and console logs I can provide. HAR is quite sensitive so let me know.
Sonoma 14.4.1 (up to date when writing this)
tested with edge,chrome,safari
deactivated ublock, and few unrelated plugin, reduced tracking prevention from strict to balanced
nothing did it

[PetMudstone]

I am having a similar problem on Windows 10, using Firefox. It did briefly authorize properly and allow imports before this error suddenly started appearing after a few attempts. However, images would just fail to import on an arbitrary basis beforehand.

[amyers1616]

Can confirm error on Linux and Windows 10 too.

[robbbyn]

Same error for me on Firefox on Windows 10. Auth worked initially, however the Importer did not import properly; subsequent attempts to auth again then failed afterwards.

[GregHib]

Console log below, it's microsoft returning 429 (too many requests) after 5+ sign-ins. Importer doesn't seem to store and reuse the login token between imports even when pressing the "back" button after an import.

It also seems to occur when importing 50+ pages in one go.

OneNotes api is throttled to 5 concurrent requests per app per user: https://learn.microsoft.com/en-us/graph/throttling-limits#onenote-service-limits

Failed to load resource: the server responded with a status of 429 ()
An error has occurred while fetching an resource: 
{
    "error": {
        "code": "20166",
        "message": "The app has issued too many requests on behalf of this user in a short time period.",
        "innerError": {
            "date": "2024-04-19T14:39:21",
            "request-id": "c3bc1789-bd97-485b-8dfe-3bf943047d2e",
            "client-request-id": "c3bc1789-bd97-485b-8dfe-3bf943047d2e"
        }
    }
}
An error occurred while we were trying to sign you in. Error details:  TypeError: Cannot read properties of undefined (reading 'value')
    at Mr.showSectionPickerUI (plugin:obsidian-importer:214:1374)
    at async Mr.authenticateUser (plugin:obsidian-importer:214:716)

[GregHib]

This bug would be that the error isn't properly displayed to the user. The actual solution would be #117

[HavenAdventures]

I'm not even getting one import to work before getting this error. My issue does not to be related to a timeout

[enoola]

I'm not even getting one import to work before getting this error. My issue does not to be related to a timeout
I have the same output as @fjacquet , but without a glance at it working at all.
so the error

{"An error has occurred while fetching an resource:",{"error":{"code":"10008","message":"One or more of the document libraries on the user or group's OneDrive contains more than 5,000 OneNote items (notebooks, sections, section groups) and cannot be queried using the API. Please make sure that none of the user or group's document libraries contains more than 5,000 OneNote items. Browse to this page for more information: https://blogs.msdn.microsoft.com/onenotedev/2016/09/11/onenote-api-calls-fail-with-a-large-number-of-items-in-a-sharepoint-document-library/","innerError":{"date":"2024-04-26T00:11:47","request-id":"81b24599-d7a6-4ed7-b569-036d3dfb4826","client-request-id":"81b24599-d7a6-4ed7-b569-036d3dfb4826"}}}

to note : " the user or group's OneDrive contains more than 5,000 OneNote items .. cannot be queried ..."
=> https://blogs.msdn.microsoft.com/onenotedev/2016/09/11/onenote-api-calls-fail-with-a-large-number-of-items-in-a-sharepoint-document-library

In essence I agree with @GregHib , pointing out the limitation and a link to the above would be a solution AFAIK.
now I need to find or make something to split my object across multiple users :D

[xinzihou]

Same issue on Chrome and MacOS 10.13. I've imported twice successfully and from the third time this error occurred. I've been logged in my OneNote account all time.

[RavHilton]

Same issue here when authing through an Opera browser - some data imports, then it consistently fails. Retrying just leaves me with this error and no further hope of importing...

[RavHilton]

Importer just updated to 1.6.4 and the same error remains...

[jidloyola]

just encountered the same issue. Has anybody found a solution yet?
This was the error message I got:

[marc-signer]

I'm experiencing the same problem and can confirm that my console also says it is due to a 429 (Too Many Requests) error.
It occured each time after the import of a rather large notebook that failed halfway through (also because of too many requests). After waiting a day and trying again, the login worked but I got to the same point again after trying to import a larger notebook.
I'm on Windows / Chrome.

Is there a solution or a workaround to this problem? Doesn't seem like there's a whole lot one can do as an end user and it's kinda frustrating.

[varju]

Is there a solution or a workaround to this problem? Doesn't seem like there's a whole lot one can do as an end user and it's kinda frustrating.

In my case I split my notebook into smaller sections and imported the sections one at a time, with a break each time I started getting 429 errors.

[marc-signer]

@varju Oh alright, tysm for the tip! Have you found out what roughly the maximum amount of pages is that can be handled without throwing an error? And by splitting do you mean just split the selection of the import or literally split the notebook?

[varju]

@varju Oh alright, tysm for the tip! Have you found out what roughly the maximum amount of pages is that can be handled without throwing an error? And by splitting do you mean just split the selection of the import or literally split the notebook?

In my case I only had one large notebook with several large sections. I rearranged my sections into chunks of about 50 notes each. I think I was able to import 2 or 3 of these sections before it started rate limiting again. Larger than 50 and the initial section query tended to time out, aborting the import with a different hidden error.

Problems were compounded for me because it turns out many of my notes had never synced to the cloud, causing 404s during import. I had to manually force syncing on each note, likely consuming more of my quota.