Skip to main content

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools
Changelog
Governance

Recurring tasks follow their deadline

A recurring task now stays active until its deadline. Probo creates the next task when that date passes, using the previous deadline plus the recurrence interval to set its due date.

Recurring tasks follow their deadline screenshot

Recurring tasks now advance on their due date, not when someone marks the current task complete. The task stays in its series until the deadline passes.

Probo then creates the next occurrence and sets its deadline from the previous one plus the recurrence interval. A late task no longer shifts every future due date.