[09:14:02] Customer (Maya R.): Hi, I'm trying to publish the fall service changes in the municipal transit planner, but the trip planner preview is still showing the summer schedules.

[09:14:18] Support (Daniel): Good morning, Maya. I can help with that. Are you working in the "Fall 2026 Draft" scenario or the approved service board version?

[09:14:37] Customer (Maya R.): Fall 2026 Draft. We imported the GTFS file yesterday afternoon and validated it with no critical errors.

[09:15:05] Support (Daniel): Thanks. If validation passed but preview still shows old trips, the preview cache may still be tied to the active baseline. Can you confirm whether the scenario status is set to "Ready for Review" or still "Editing"?

[09:15:29] Customer (Maya R.): It says "Editing." I didn't realize that affected the public preview.

[09:15:55] Support (Daniel): It does for the public-facing preview. While a scenario is in Editing, the internal map updates, but customer itinerary results continue using the current published schedule.

[09:16:22] Customer (Maya R.): That explains it. We also changed stop 1842 to temporary closure for construction. Will that carry over when I move it to review?

[09:16:49] Support (Daniel): Yes, as long as the closure is attached to the same effective date range as the fall schedule. Could you check the closure dates on stop 1842?

[09:17:31] Customer (Maya R.): It is set from September 1 to November 15. The fall schedule starts September 3.

[09:17:58] Support (Daniel): That should work. After you change the scenario to Ready for Review, run "Generate Planner Preview." It usually takes 3 to 5 minutes for routing, stop alerts, and transfer rules to rebuild.

[09:18:24] Customer (Maya R.): I see that option now. Should I worry about the warning for route 7 saying "short transfer window at Central Station"?

[09:18:51] Support (Daniel): That warning means at least one scheduled connection is below your city's minimum transfer threshold. It will not block publishing, but riders may see tight connections in results.

[09:19:16] Customer (Maya R.): The minimum is 6 minutes, and we have one 4-minute connection after 8 PM. Operations approved it because it is the same platform.

[09:19:42] Support (Daniel): In that case, you can add a station-level transfer exception for Central Station after 8 PM, or leave the warning documented in the approval notes.

[09:20:08] Customer (Maya R.): I'll add the exception. One more question: the accessibility layer shows two closed elevators, but facilities told us one reopened this morning.

[09:20:36] Support (Daniel): Elevator status is pulled from the facilities feed every 15 minutes. If it reopened this morning but still shows closed, the source record may not have been cleared.

[09:21:02] Customer (Maya R.): Got it. I will check with facilities before we publish.

[09:21:26] Support (Daniel): Good plan. Once the scenario is Ready for Review and the preview is generated, test a few sample trips using September 4 as the travel date. That will confirm the fall schedules are being used.

[09:21:49] Customer (Maya R.): I changed it to Ready for Review and started Generate Planner Preview. It says queued.

[09:22:11] Support (Daniel): Perfect. Leave that running. When it finishes, the preview banner should say "Fall 2026 Draft" with the generated timestamp.

[09:25:44] Customer (Maya R.): It completed. I searched Maple & 3rd to Central Station for September 4, and now it shows the new route 7 timing.

[09:26:03] Support (Daniel): Great. That confirms the schedule import is active in the planner preview.

[09:26:28] Customer (Maya R.): Thanks. The issue was the scenario status and preview generation step.

[09:26:45] Support (Daniel): You're welcome. I'll note that the schedule preview was resolved by moving the scenario to Ready for Review and regenerating the planner preview.