Expired items do not change status to Expired

Expired items do not change status to Expired

avatar

Hello Devolutions,

I have tried to search for an equivalent issue, but I came up empty.

When our items expire, they correctly appear in the dashboard under "Expired Entries". However, the status on the expired entries does not change to "expired"

According to the documentation, Status - Devolutions Documentation, it can set it "... automatically if the session expiration date is set in his property"
Are we missing a configuration somewhere?

We set the expiration date under description of the items.

Can you help us out?

Best regards

All Comments (4)

avatar

Hello,

This is the normal behavior currently. In the UI the entry will be marked as expired which is effectively the same as having the "expired" status. For example, in the navigation pane the entry will be red with the [expired] flag in its name.

Is there a reason why you specifically need the status to be set to expired when your entry expires?

Regards,

Hubert Mireault

avatar

Let me correct myself, the status is also set as expired automatically, provided there wasn't another status configured on the entry beforehand. My question still stands though, I may not be understanding what's not working properly for you and what you'd like to achieve, so having more information on what you're trying to do would be helpful.

Regards,

Hubert Mireault

avatar

Hi Hubert!

Thank you for your reply and sorry that it took so long for me to get back to you.

The expired tag did actually automatically happen. But it seemed that restarting the app was necessary.

The tag was correctly added to the test entry for me, while on a coworkers PC it didn't.

It seems like it was some synchronization delay or that it doesn't change the status unless you restart the app.

Anyway, thank you for your help!

Best regards

avatar

Hello,

Thank you for the feedback. It's possible that your coworker needed to do a full refresh or similar to trigger seeing the change, and restarting the application would achieve this. Doing the Ctrl-F5 shortcut should work as well. Be aware that it may take some time since doing a full refresh clears the cache, depending on the size of your database and the latency to it.

Let us know if you encounter any other issue or missing feature and we'd be happy to help!

Regards,

Hubert Mireault