Custom

Table of Content

⚠️ Known Issue

@now Function Not Working Correctly After Template Duplication

We’ve recently identified an issue affecting a number of users after downloading the LiFE RPG template.

❗ What’s happening?

Due to a recent Notion update, we’ve found that the @now function may no longer behave as intended after duplicating the template into your workspace.

Instead of remaining a dynamic @now value, it may automatically convert into a fixed timestamp (the moment you duplicated the template).

🧩 How this affects your system

This can lead to incorrect timestamps in areas such as:

  • Habit tracking (Good Habit / Bad Habit check-ins)

  • Task Sessions (Start Time tracking)

For example:

  • Your habit logs may not reflect today’s date

  • Task sessions may show incorrect or outdated start times


🔍 Current status

We are actively investigating this issue.

At the moment, we have not been able to reliably reproduce it on our end, which makes it difficult to identify the exact root cause.

What we do know:

  • The template is correctly configured with the @now function

  • However, once duplicated into a user’s workspace, the function may change unexpectedly

This issue did not exist when LiFE RPG 2.0 was first released, and only started appearing around March 2026.


🤔 Possible causes (unconfirmed)

Our current suspicions include:

  • Notion converting @now into a fixed timestamp during duplication

  • Timezone-related inconsistencies affecting how @now is interpreted

We’re still working to confirm the exact cause.


🛠 Temporary fixes (workarounds)

While we investigate, here are some temporary solutions you can follow to fix the affected parts:

1. Habit Tracker (incorrect log date)

If your habit check-ins are not logging the correct date, follow this guide:
👉 https://resources.heyalbert.co/share/6FHFP8yLxSvZr9g85aaAIlS3W

2. Task Sessions (incorrect start time)

If your task session start time is incorrect, follow this guide:
👉 https://resources.heyalbert.co/share/h45DgUyN7WrfNZjM5xJyPUqyP


🙏 We need your help

If you’ve experienced this issue and have any insights at all (even small details), please reach out to us at:

📩 contact@heyalbert.co

Your input could help us identify the root cause faster and prevent this from affecting more users.


💬 Final note

We’re really sorry that this issue is happening. Our goal has always been for LiFE RPG to work seamlessly right after download, without requiring extra setup or fixes.

We’re actively working on a proper solution and will roll out updates as soon as we have one.

In the meantime, if you run into any other issues, feel free to reach out. I personally read and reply to almost every email.

Thanks again for your support, it truly means a lot 🤍

- Albert

@now Function Not Working Correctly After Template Duplication

We’ve recently identified an issue affecting a number of users after downloading the LiFE RPG template.

❗ What’s happening?

Due to a recent Notion update, we’ve found that the @now function may no longer behave as intended after duplicating the template into your workspace.

Instead of remaining a dynamic @now value, it may automatically convert into a fixed timestamp (the moment you duplicated the template).

🧩 How this affects your system

This can lead to incorrect timestamps in areas such as:

  • Habit tracking (Good Habit / Bad Habit check-ins)

  • Task Sessions (Start Time tracking)

For example:

  • Your habit logs may not reflect today’s date

  • Task sessions may show incorrect or outdated start times


🔍 Current status

We are actively investigating this issue.

At the moment, we have not been able to reliably reproduce it on our end, which makes it difficult to identify the exact root cause.

What we do know:

  • The template is correctly configured with the @now function

  • However, once duplicated into a user’s workspace, the function may change unexpectedly

This issue did not exist when LiFE RPG 2.0 was first released, and only started appearing around March 2026.


🤔 Possible causes (unconfirmed)

Our current suspicions include:

  • Notion converting @now into a fixed timestamp during duplication

  • Timezone-related inconsistencies affecting how @now is interpreted

We’re still working to confirm the exact cause.


🛠 Temporary fixes (workarounds)

While we investigate, here are some temporary solutions you can follow to fix the affected parts:

1. Habit Tracker (incorrect log date)

If your habit check-ins are not logging the correct date, follow this guide:
👉 https://resources.heyalbert.co/share/6FHFP8yLxSvZr9g85aaAIlS3W

2. Task Sessions (incorrect start time)

If your task session start time is incorrect, follow this guide:
👉 https://resources.heyalbert.co/share/h45DgUyN7WrfNZjM5xJyPUqyP


🙏 We need your help

If you’ve experienced this issue and have any insights at all (even small details), please reach out to us at:

📩 contact@heyalbert.co

Your input could help us identify the root cause faster and prevent this from affecting more users.


💬 Final note

We’re really sorry that this issue is happening. Our goal has always been for LiFE RPG to work seamlessly right after download, without requiring extra setup or fixes.

We’re actively working on a proper solution and will roll out updates as soon as we have one.

In the meantime, if you run into any other issues, feel free to reach out. I personally read and reply to almost every email.

Thanks again for your support, it truly means a lot 🤍

- Albert

@now Function Not Working Correctly After Template Duplication

We’ve recently identified an issue affecting a number of users after downloading the LiFE RPG template.

❗ What’s happening?

Due to a recent Notion update, we’ve found that the @now function may no longer behave as intended after duplicating the template into your workspace.

Instead of remaining a dynamic @now value, it may automatically convert into a fixed timestamp (the moment you duplicated the template).

🧩 How this affects your system

This can lead to incorrect timestamps in areas such as:

  • Habit tracking (Good Habit / Bad Habit check-ins)

  • Task Sessions (Start Time tracking)

For example:

  • Your habit logs may not reflect today’s date

  • Task sessions may show incorrect or outdated start times


🔍 Current status

We are actively investigating this issue.

At the moment, we have not been able to reliably reproduce it on our end, which makes it difficult to identify the exact root cause.

What we do know:

  • The template is correctly configured with the @now function

  • However, once duplicated into a user’s workspace, the function may change unexpectedly

This issue did not exist when LiFE RPG 2.0 was first released, and only started appearing around March 2026.


🤔 Possible causes (unconfirmed)

Our current suspicions include:

  • Notion converting @now into a fixed timestamp during duplication

  • Timezone-related inconsistencies affecting how @now is interpreted

We’re still working to confirm the exact cause.


🛠 Temporary fixes (workarounds)

While we investigate, here are some temporary solutions you can follow to fix the affected parts:

1. Habit Tracker (incorrect log date)

If your habit check-ins are not logging the correct date, follow this guide:
👉 https://resources.heyalbert.co/share/6FHFP8yLxSvZr9g85aaAIlS3W

2. Task Sessions (incorrect start time)

If your task session start time is incorrect, follow this guide:
👉 https://resources.heyalbert.co/share/h45DgUyN7WrfNZjM5xJyPUqyP


🙏 We need your help

If you’ve experienced this issue and have any insights at all (even small details), please reach out to us at:

📩 contact@heyalbert.co

Your input could help us identify the root cause faster and prevent this from affecting more users.


💬 Final note

We’re really sorry that this issue is happening. Our goal has always been for LiFE RPG to work seamlessly right after download, without requiring extra setup or fixes.

We’re actively working on a proper solution and will roll out updates as soon as we have one.

In the meantime, if you run into any other issues, feel free to reach out. I personally read and reply to almost every email.

Thanks again for your support, it truly means a lot 🤍

- Albert