This allows for future calls from arguments / associations
Screen state may have changed at an inopportune moment. Run on local scheduler, not API scheduler to avoid any weirdness.
Previously it may have gotten blocked by being in a sub screen.
For all usages, it looks like this was unnecessary.
since it's been fixed in a framework
because it's disabled