Page Lifecycle

You might say

After I change a booking and return to the list, why is the old time still there?

Callbacks triggered when a page is created, shown, hidden, or unloadedIn a mini program, opening a booking detail page can hide the list while keeping its instance. Returning shows that same list again and triggers onShow, not another onLoad. Choose refresh and cleanup timing based on those events.

Know first

Mini Program State

onLoadonShowonHideonUnload

Is the list page recreated when you return?

Standard page navigationlist

My bookings

Pottery workshop

14:00

View booking details

Triggered page callbacks

list.onLoad
list.onShow
list.onReady

Creating the list instance triggers onLoad and onReady once in this example.

When should work happen?

Initialize once for this instance: onLoad handles initial parameters; onReady indicates the initial view is ready. Neither callback means a data request has completed.

Respond when the page reappears: onShow can run multiple times on the same instance. Refresh data that may have changed; onHide can pause work and onUnload can clean up resources.

Quick checkChoose the best answer

Booking details were updated. navigateBack shows the existing list, but refresh currently runs only in onLoad. What should be checked?

Put the refresh in list.onReady insteadWait for list.onUnload before refreshingRefresh the changed booking when list.onShow runs

Send this to the AI Agent in your project

After editing booking details, the list still shows the old time on return. Check the page lifecycle: is data loaded only in onLoad, and should onShow refresh it? Repeat entering details, editing, and returning twice; verify the latest booking appears without duplicate requests.

Learn next

1Mini Program→2State→

Recommended tool

Web fine-tuning tool · Selector Pro

Select page elements for precise AI edits

Click a button, text, or card, note the change, then copy its exact location to AI.

Open Selector Pro website