Dispel | Disassembler for 65816/SNES rom images | Reverse Engineering library

There's no public official information regarding the exact period this is referring to.

Nevertheless, after some testing, it seems like the short periods of time are longer than what your workflow would require.

Since the limit that is troubling you is calendar creation (from Avoid Calendar use limits):

If you create more than 60 new calendars in a short period, your calendar might go into read-only mode for several hours.

I did some tests with a Workspace account, in order to see what's the maximum rate of calendar creation that won't result in this limit being exceeded.

More specifically, I tried creating calendars periodically, with several different periods, ranging from 5 seconds to 15 minutes.

For most of these periods (from 5 seconds to 10 minutes at least), the following exception started showing up after creating 40-something calendars approximately:

You have been creating or deleting too many calendars or calendar events in a short time

After this, no more calendars could be created for some time.

For 15-minute period, I got the error after creating around 80-something calendars, so I guess the maximum rate of creation is close from there (1 calendar created every >15 minutes). Since this rate is not disclosed, though, it could change without notice, so take this with a grain of salt.

The original poster, GorgeousPuree, also made some testing, with results in accordance with what I got (see comment):

I also made my expirements and I've got a timeout after 25 calendars in 1 and 3 minutes intervals.

In any case, the short period seems to be way too long for the worst case scenario:

60 calendars in 5 mins

After some ramblings trying to figure this out got to the root cause.

When using node -r esm index.js, the esm package does already all the work for your (as noted in other answers), and therefore (not mentioned in other answers):

• the package.json should be updated by removing "type:" "module" (as it creates unintended interactions between the native node ES Modules feature and the esm package you installed)

Aside note: if you tried to use node ES Modules and then you try to switch to esm package, it is very easy to miss this point.

Traversal' is a type synonym for a type containing forall, which makes it a second class citizen in the type system: we can't instantiate a type variable with such a type.

In particular, here we are trying to do so with foldr :: (a -> b -> b) -> b -> [a] -> b, we can't instantiate b = Traversal' _ _, because Traversal' contains a forall.

One work around is to wrap Traversal' in a newtype, ReifiedTraversal. Wrap (using the Traversal constructor) before passing at 1 to foldr; inside foldr, unwrap to use adjoin, and rewrap; unwrap at the end.

EXO is using Azure AD as the user directory. This means that changes made for a user in Azure AD will automatically be reflected in EXO (where relevant, of course).

If you want to ensure the previous email address as an alias I suggest you set this in EXO as part of your scripting.

Change html like this: