If the value is extremely repetitive I would omit it completely from the list item itself. Place and show it in a parent container and group the items based on their "date" value.
Edit: Example where the grouping is done on page to page basis and the whole data set has the same value for the period.
Option B would better suit experienced users (power-users) as they would be, through working with the system and/or the data the system is working with, more familiar with the data and how it is presented and managed/transformed by the system. I.e. it could increase productivity.
So, a way to leverage both Option A and B in a system in order to provide a ...
Since the message box already explains the error, the Try later can be embedded within that message.
I'm not sure what all the possibilities of errors where you would need to use that message box are, but "Okay", "Got it" or "Close" will cover all use cases where you need to show a secondary action button after an error message description.
For instance, ...
You can create a field set for the time input. One way to do it could be to choose a field - set heading, such as 'Walk times'. Under this heading, you can show multiple fields as per the user's chosen frequency.
For labels, it's probably best to keep the context of the walks. So the labels could just be:
First walk: &...