Refresh answers and request role rechecks after a change
What It Does
A registered record-event consumer, a system reconciliation request or a publication asks to refresh subjects and their derived roles.
The Flow
Deliver up to one hundred events from a stream to Platform’s change handler. Check whether an active event-refresh declaration reads the stream dataset; otherwise acknowledge without refresh. Invalidate subject-indexed answers, queue role checks and nudge dispatch for affected subjects. Accept a bounded system reconciliation request and deduplicate its subject checks. Dispatch waiting requests every minute or on nudge, then have Security evaluate and synchronize rule-derived grants.
When Something Fails
The originating event consumer owns retry and dead-letter handling. No events arrive until the handler is registered. An ignored stream needs no retry. Current time-only CRM declarations leave display cache until expiry and roles until other refresh paths. Return failed workspace events for retry while preserving other workspaces’ successes. Route caches without subject indexing survive up to two minutes. Invalid requests enqueue nothing. Existing pending work remains unchanged. Retry can end in dead-lettering; a missing binding fails the subject’s batch. Prior grants remain until their twenty-four-hour expiry or a successful refresh.
Open Design Questions
Publication atomically requests current holder rechecks and bounded simulation gains.