Originator map from Eagon didn't use my atlas passive tree

Originator map from Eagon didn't use my atlas passive tree. Inside the map there were league mechanics blocked by my atlas, it didn't have buffs from atlas passives (for example, strongboxes always rare; it was what made me realize)etc. Happend once, next strand or w/e its called, a next map in succesion, was all good. I used a bunch of ambush scarabs and 1 expedition. Map was chiseled, rare. it was Mesa, I think?
Also worth mentioning, yesterday when I started Eagon map, I lost internet. Then I'd came back next day, have absolutely none of my scarabs/map mods in his 'map-device' interface'-just a white map. That map didn't use my atlas passive tree, which could point us to why it happend.

This happened to me too. I'm pretty sure they used my points in the past?

Blocked league mechanics can show up if you were accidentally on the wrong tree or if you added them with the end of the map buff. IE: Block Ritual, but then pick "map contains Rituals" as a buff will cause Rituals to spawn for the remaining maps in the chain.

As for league mechanics not showing up, the conditions can be wrong tree again, the map is cursed (map modifier generated causing reduced quant and reduced league content generation), or maybe put in the wrong scarabs.

I know once I swapped tree + scarabs mid-chain because I hit a certain modifier, and then forgot about it until I saw Maven again at the start of the next chain. Since the map device is separate, I had 2 different sets of scarabs.

Aaaaaand it happend again. A t16.5 map that did use my scarabs from eagon map device, but it did NOT use my atlas. No changes were done to the atlas/map device between map before and a map afterewards. Other maps worked fine, as they do 95/100 times.