Unable to add more days to routine

[jmccaull]

Priority/Impact

Medium (affects some functionality)

Description

I attempted to restore routines from a psql backup following the docs but had some issues, I think with table constraints. Eventually I just restored the manager tables and updated the sequence numbers then was able to see my routine and template. When editing these, I was getting errors from the webui with red text that look like regexes. I was able to duplicate the routine and then edit it further but I am not able to add new days, they are persisted in the edit page, but not showing in the view page. I further tried to duplicate the copy but this now causes the last day from the original to not be displayed and I am still not able to add any more days.

Inspecting the traffic it seems /api/v2/routine/16/date-sequence-display/ does not have the missing days but /api/v2/routine/16/structure/ does.

I've tried running makemigrations and migrate in the web container which looked successful but see no changes.

Any idea how I can fix this without recreating the routine from scratch?

Server version

2.5.0a2+git3cc13ad

Mobile app version

No response

[jmccaull]

This is the file I restored from

routine.sql

note: it does not contain the lines to update the sequence numbers, I did those by hand, ex:
SELECT setval(pg_get_serial_sequence('manager_maxrepetitionsconfig', 'id'), (SELECT MAX(id) FROM manager_maxrepetitionsconfig) + 1);

[jmccaull]

I accidentally just discovered it was the end date causing the days to be cut off. Once adjusting I'm seeing all the days now., this can be closed and hopefully helps someone in the future.

It might be nice to make the fixed weekly schedule toggle a set of radio buttons with options like: fixed weekly, fixed end date, projected end date based on days.

[paigefletcher1282-code]

Thanks for the update! Glad you found the end date was the culprit. Do you think the suggested toggle for end date options would make things clearer for future users?

…

On Wed, Mar 25, 2026, 9:52 PM John McCaulley ***@***.***> wrote: *jmccaull* left a comment (wger-project/wger#2266) <#2266 (comment)> I accidentally just discovered it was the end date causing the days to be cut off. Once adjusting I'm seeing all the days now., this can be closed and hopefully helps someone in the future. It might be nice to make the fixed weekly schedule toggle a set of radio buttons with options like: fixed weekly, fixed end date, projected end date based on days. — Reply to this email directly, view it on GitHub <#2266?email_source=notifications&email_token=B7BB4JRECAH6CZOAU7I3OS34SSEN3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJTGA4TQMZTGUZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4130983353>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7BB4JQVFU74RWM5ST7B2F34SSEN3AVCNFSM6AAAAACW7LOK7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMZQHE4DGMZVGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jmccaull]

It would but maybe clarifying the docs would help just as well. I'm not using routines the way it seems they are intended so that probably has a lot to do with it too.

I do a lot of bodybuilding style lifting workouts with periodization. They are very difficult to create a rotating repeating schedule, sometimes even switching variations of lifts between each week for each period. I would end up needing to set up sets of 1-2 week routines in a row. It ends up being somewhat difficult to track or create templates for. A much easier approach has just been to shove it all into a single routine that does not repeat, hence the end date confusion.

I was actually going to create a feature request to suggest adding "workout plans" as one time linearly progressing sets of workout days in addition to routines to address this. It seems like I see a lot of requests for dynamic tracking of workouts between here and the flutter app that might fit under this well. I spent a little time going through the table structure for routines trying to restore a backup and I was going to further suggest looking at backing this feature with documents instead of relational tables. At some point I'll get time to create a dedicated issue/feature request and try to come up with a pull request.