Job Ledger thread IDs go stale

[sjstein]

It appears that after some amount of time, a link to a job ledger thread within a job post goes stale and shows up as #unknown instead of actually linking to the job ledger. This may be causing problems when an older job is crewed and the bot scrapes the post, finds a job ledger post, but cannot access the thread due to the link being funky (missing).

For example, this post originally showed:
[r8TE JOB ADMIN] 2025-11-02 14:02:27 NEW LEDGER JOBID# 251102-15050384 | (BAR) G-ROSKIN [Loaded Grain to HNM] ⁠#unknown

interestingly, after I found the post in the ledger forum, it then showed up properly:

[r8TE JOB ADMIN] 2025-11-02 14:02:27 NEW LEDGER JOBID# 251102-15050384 | (BAR) G-ROSKIN [Loaded Grain to HNM] ⁠251102-15050384 | (BAR) G-ROSKI…

Need to determine if the bot can search within the ledger thread a bit deeper than just trusting that link

[TheGrayGryphon]

Something to chew on, food for thought, etc.: https://www.reddit.com/r/discordapp/comments/1evpxxa/how_do_i_stop_threads_from_saying_unknown/

It appears in the reference for this case - https://discord.com/channels/1326223785086423080/1434579548191850739 - it is because if there is greater than "one month" of inactivity between interactions, Discord will assume a post in a forum is "closed."

I would assume that if the ledger posts remain active, then the links to the posts should stay active. I imagine Discord does this to keep cache sizes down? Or at least something to that effect.

A potential solution would be to say, if ledger thread is about to go stale (certain amount of time since last message sent in thread) send a new message, then delete the new message? Perhaps the new message would need to stay?