Access control configuration queue

Select Configuration Status under Physical Access Control Settings, or select a controller's Pending Updates badge. This queue is the operational record of commands waiting for or reporting controller delivery.

Filter the queue

Filter by Site, Controller, and Status. Status defaults to Enabled, which is normally the most useful pending-work view.

Platform administrators can choose all sites. Other users receive their assigned sites, including the site used to open the dialog. A controller-specific entry point preselects that controller.

The grid shows:

• site and controller;
• command;
• credential when the command concerns one;
• push result;
• push-request date;
• enabled state;
• data and file path for Administrator-level users only.

Disabled rows appear in red. The request date is displayed from the stored value without site-time-zone formatting, so account for server/UTC interpretation when comparing it with local events.

Interpret status

An Enabled queue row is eligible for processing. A Disabled row is retained but not eligible. Push Result describes the last recorded controller response when one exists; a blank result can mean the command has not completed or has not reported a result.

The queue is not a physical-access test. A successful return code does not prove wiring, strike behavior, reader association, schedule logic, or credential encoding.

Enable or disable commands

Select one or more rows and choose Enable or Disable. The action updates the selected records and records audit history.

Disabling is useful for pausing work while investigating a bad mapping. It does not recall a command that a worker or controller already consumed. After disabling, refresh and confirm the row state, then inspect controller activity before assuming delivery stopped.

Re-enabling makes retained work eligible again. Verify that its data is still valid; an older command can conflict with a newer portal configuration.

Remove commands

Remove permanently deletes the selected queue records after confirmation. Removing a row does not reverse a command already applied by a controller and does not repair the underlying portal record.

Keep failed rows until you have captured the command, controller, request time, result, and related credential or configuration. Remove them only under the site's queue-retention procedure.

Investigate a failed or stuck command

1. Confirm the selected site and controller.
2. Review Enabled, command type, request time, and result.
3. Check controller health and last-seen state.
4. Verify the source record's external IDs and associations.
5. Correct the source configuration before retrying or re-enabling.
6. Refresh the queue and test at the affected opening.

See Troubleshooting for common dependency and delivery failures.