Skip to content

fix(dashboard): persist lastRun so scheduling KPIs stay in sync#327

Closed
RaminGe wants to merge 1 commit into
orangecoding:masterfrom
RaminGe:fix/dashboard-last-next-run
Closed

fix(dashboard): persist lastRun so scheduling KPIs stay in sync#327
RaminGe wants to merge 1 commit into
orangecoding:masterfrom
RaminGe:fix/dashboard-last-next-run

Conversation

@RaminGe

@RaminGe RaminGe commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

lastRun was only updated on the startup settings object while the dashboard reads a rebuilt cache after upsertSettings invalidates it.

Fixes: #324

lastRun was only updated on the startup settings object while the
dashboard reads a rebuilt cache after upsertSettings invalidates it.
@orangecoding

Copy link
Copy Markdown
Owner

Hey @RaminGe

there was already a pr in the past which I closed. See #303

It's correct that this is not stored in the settings, simply because it is not a setting. I have not seen a value yet in storing this information in the db, but if I would, I certainly would store it as part of the job :)

I'll keep your change in mind and will do it at a later stage. Thanks for your contribution though!

@RaminGe RaminGe deleted the fix/dashboard-last-next-run branch June 9, 2026 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Last and Next search in dashboard are wrong

2 participants