On refresh, the generated schedule goes away. This is probably because it's not saving data between "sessions" (idk if that's actually the right term). For the conflicts and incompletes, the data reappears after refresh because it is actually making the get request every time.
Potential fix: AFTER the schedule is generated once, assuming it is still stored on the backend, we have a new endpoint to fetch the schedule. That way every refresh it refetches the data.
On refresh, the generated schedule goes away. This is probably because it's not saving data between "sessions" (idk if that's actually the right term). For the conflicts and incompletes, the data reappears after refresh because it is actually making the get request every time.
Potential fix: AFTER the schedule is generated once, assuming it is still stored on the backend, we have a new endpoint to fetch the schedule. That way every refresh it refetches the data.