Appearance
Configuration Revisions and Proposals
Ordyn records changes to configuration, including jobs, scripts, credentials and assignments. Use an item's Overview to inspect its current settings and Revisions to compare settings or restore an earlier revision. For items listed in a table, select the item and choose Revisions from its context menu. Protected values stay hidden; the comparison shows whether they changed.
Review and compare revisions
Edit an item and select Save to apply your changes. Each successful change appears in Revisions with its author and time. If someone else saved the item after you opened it, reload it and review their change before saving again.
Select a revision to read its complete configuration, or select two revisions to compare them side by side. You can also compare an earlier revision with the current settings. Nested settings, task order and script changes appear in the comparison. Operational results, endpoint inventory and job runs are separate from configuration history.
Processing status
Processing status shows whether Ordyn has completed the follow-up work for a saved change, such as publishing updated settings to a service. It appears in revisions and applied proposals.
| Status | Meaning |
|---|---|
| Not required | The change needs no follow-up processing. |
| Pending | Processing is waiting, running or awaiting an automatic retry. |
| Completed | Ordyn finished processing the change. |
| Failed | Processing failed and automatic retries were exhausted. |
| Waiting for earlier revision | Processing for an earlier revision of the same item must finish first. |
The configuration is saved before this processing runs. A pending or failed status does not undo the saved change, and Completed does not confirm that an endpoint has received or applied the settings.
If processing fails, users with editing access can choose Retry processing from the revision's context menu, its details or the applied proposal. When an earlier revision blocks progress, the action retries the failed work for that revision. Retrying does not create another revision or apply the proposal again.
Restore a revision
Open Revisions, select an earlier revision, and choose Restore from its context menu. Confirm to apply its recorded settings. A restoration creates and opens a new revision and keeps the intervening history. For files, this restores their settings; manage content separately in Versions.
Restoration uses your current editing access and requires the referenced resources to be available. It does not restore related resources automatically or undo work already performed on endpoints. A deleted item can be restored when its original location and dependencies are available. Some historical formats can be inspected without being restorable.
Delete historical revisions
Select older revisions and choose Delete revisions from the context menu. Deletion permanently removes their comparison and restoration history. The current revision and revisions needed by open proposals or unfinished processing are protected.
Deleting configuration history does not delete file content. Manage content retention in Files.
Review agent proposals
AI agents submit proposals for review by default. Agents granted Review proposals can also approve or reject them, and Apply automatically applies an agent’s own proposals on submission. Use Operations → Proposals to review all submitted proposals, including new items. An item's Pending changes action opens its proposal directly, or filters the Proposals table to that item when several proposals exist. Clear the entity filter in the Proposal column to see proposals for other items.
The review includes every change in the proposal. New items show their proposed settings; changes to existing items show the current and proposed settings side by side. Select Approve and apply to apply the whole proposal, or Reject. Feedback is optional for either decision. You need editing access to every change in the proposal. See AI agents for agent setup.
Proposal review activity identifies the reviewer and marks automatic application. Applied revisions show Proposed by and Applied by, with a link to the proposal when you have access. Pending proposals appear in Proposals until applied.
A submitted proposal cannot be edited. If the active configuration or a dependency changed after review, the agent must submit a replacement for fresh review. A failed application leaves active configuration unchanged. For failures after application, see Processing status.
Audit and endpoint History
Audit records activity and who performed it. Configuration audit entries provide View revision and, when available, View changes for the exact saved configuration. These links require access to the configuration. Older events may only include their recorded change details.
An endpoint's History contains operational activity such as job runs and sessions. Its Revisions tab contains configuration versions. See Audit and History.
Storage
Configuration revisions remain available independently of audit retention, including after an item is deleted. File retention determines whether referenced content remains available to download or restore.
Super administrators can inspect storage use under Reporting → Configuration storage. History only identifies content referenced by earlier revisions rather than current configuration; other resources may still need it.