Custom attributes not saving in Hexnode portal with no errorSolved

Participant
Discussion
3 days ago Oct 05, 2026

I’m trying to add a new custom attribute in the Hexnode portal, but after saving it, nothing shows up on the custom attributes page. I was able to create one the previous day, so this started suddenly.

There’s no error message on the page. I tried a normal browser session and incognito, but the result was the same. Browser console and network checks did not show failed requests like 400, 401, or 500 errors. A few other portal actions also seemed odd around the same time, such as sign-out not behaving consistently.

Is there a limit on how many custom attributes can be added, or could this be related to technician permissions?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
3 days ago Oct 05, 2026
Marked SolutionPending Review

Hi @grace_t, there is no daily limit that prevents you from adding custom attributes after creating one successfully the previous day.

For this behavior, the first things to rule out are:

  1. Technician role permissions

    If the signed-in technician is assigned a custom role, confirm that the role has the required permissions to manage custom attributes. If the user is a Super Admin or an admin role with the required access, this is unlikely to be the cause.

  2. Browser/session issues

    Testing in an incognito/private window or another browser helps rule out cached portal data or extensions. Since the issue persists there as well, this is less likely to be browser-specific.

  3. Failed portal requests

    If there are no visible errors and no failed network requests, the save action may be reaching the portal but the new attribute may not be reflected due to a temporary backend synchronization issue.

In the reported scenario, the behavior was caused by a temporary backend sync delay. Once that was resolved, newly created custom attributes started saving and appearing normally again.

Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
3 days ago Oct 05, 2026
Marked SolutionPending Review

In my case, the technician account already had admin access and nothing was changed in the role settings. The weird part was that the portal acted like the attribute was created, but the attribute list never updated.

Marked SolutionPending Review
Hexnode Expert
3 days ago Oct 05, 2026
Marked SolutionPending Review

If the role permissions were unchanged and the same technician could create custom attributes earlier, permissions would not be the primary suspect.

A permission-related issue usually results in restricted access, a disabled option, or an authorization-type failure. A silent save where the new custom attribute does not appear, especially when it happens across browser sessions and no failed requests are visible, points more toward a portal-side sync problem.

After the sync delay is resolved, retry creating the custom attribute and refresh the custom attributes page. The attribute should then appear as expected.

Regards,
Isabel Lora
Hexnode UEM

Save