After restart of n8n instance due to n8n upgrade or general server upgrades, Microsoft Outlook Trigger are not activated and will not poll automatically without intervention.
@Chrishayes94 the polling trigger restore on npm restarts has been buggy for a while, ditch the outlook trigger and use a schedule trigger feeding into the regular microsoft outlook node instead — survives restarts every time since it’s just a cron
plug your existing outlook creds into the microsoft outlook node, swap the folder ID to yours if needed, done.