Timestamp parsing issues on knowledge/instructions

[gauss1986]

The 'Created time' in the instructions pages is off.

Steps to reproduce the behavior:

1. Go to 'Knowledge - Instructions'
2. Click on 'Add an instruction' and add one.
3. The Created time shows '1768-02-29' or something that is clearly off.

The createdat field in the network is a string format of int

Desktop (please complete the following information):

• OS: mac os
• Browser: chrome

Wren UI

• Version: 0.31.2

Root Cause

• In the frontend code (wren-ui/src/utils/time.ts), time formatting utilities like getCompactTime call dayJs(time) directly.
• When called with a numeric string (e.g., "1764725636199"), dayjs parses it as a date string rather than a millisecond timestamp, resulting in a completely wrong historical date.
• This affects all usages across the frontend that pass API response timestamps directly into these utilities without normalization.

[fredalai]

Hi @gauss1986 , thanks for reporting this issue!

I tried to reproduce the problem on my side, but I'm currently not seeing the same behavior — the timestamp format I receive from the backend looks different from what’s shown in your screenshot. To help me investigate further, could you share the following details?

1. Which database you are using (e.g., PostgreSQL, SQLite, etc.)
2. Database version

This information will help us narrow down the root cause.
Thanks again for taking the time to help us debug this!

Freda