Since today’s release: child pages with a “logged-in user” Details view redirect to the parent page

Uncategorized
1

Hi everyone,

Since the front-end release published today (21 Oct 2026, around 12:53 UTC), a page in our live app no longer opens: users are sent straight back to the parent page.

Setup to reproduce

  • A login-protected page (parent).
  • A child page under it, containing a Details view whose data source is the logged-in user. No record ID is needed in the URL.

What happens
Opening the child page, from a menu link or a direct URL, starts rendering it. About 0.5 s later the user is redirected back to the parent page. There is no error in the console.

What we found

  • The new script k_1efcea6df99e9f3d5e31add5b5d0d3c246402b21.js adds a check in the scene view, checkRequiredRecordId(). For any child page containing a Details view, it calls Knack.Navigation.redirectToParentPage() when there is no record ID in the URL (Knack.hash_id empty).
  • The previous script, k_47d843f680d3a327ad076cd56b8f1c0120aaad41.js (7 Oct 2026), doesn’t have this check.
  • A Details view showing the logged-in user never has a record ID in the URL, so these pages are now redirected by mistake.

Expected: pages whose Details views use the logged-in user as source should be excluded from this check, as they worked before today.

Is anyone else seeing this? Knack team, could you take a look? On our side it blocks a page our team uses every day.

Thanks!

2

Same problem! All apps and users.

3

Hi @Romain

We are taking a look - will update you again soon.

Thanks,

Kara

4

We are rolling out a fix for this now

5

@Romain @W3Agro The fix is complete, you may need to clear your cache or do a hard refresh if you still see this behavior.

6

Everything is as expected now. Thank you!