Suggestion: Offline grace period for license verification
Posted: Fri Apr 17, 2026 2:37 am
Hello,
Iād like to raise a question regarding how the current licensing system works.
At the moment, it seems that Octane needs to validate the subscription each time a project is opened. In situations where the internet connection is unstable or temporarily unavailable, this prevents the software from launching, which can interrupt ongoing work.
Would it be possible to introduce a more flexible verification method? For instance, allowing the license to remain valid offline for a limited period ā such as several days ā before requiring another check. A weekly or periodic validation model, similar to what some other rendering tools use, would make the workflow much more reliable in environments with inconsistent connectivity.
I believe this kind of grace period would significantly improve usability without compromising the licensing system.
Thank you for taking the time to review this suggestion.
Iād like to raise a question regarding how the current licensing system works.
At the moment, it seems that Octane needs to validate the subscription each time a project is opened. In situations where the internet connection is unstable or temporarily unavailable, this prevents the software from launching, which can interrupt ongoing work.
Would it be possible to introduce a more flexible verification method? For instance, allowing the license to remain valid offline for a limited period ā such as several days ā before requiring another check. A weekly or periodic validation model, similar to what some other rendering tools use, would make the workflow much more reliable in environments with inconsistent connectivity.
I believe this kind of grace period would significantly improve usability without compromising the licensing system.
Thank you for taking the time to review this suggestion.