You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upcoming change: Chain reactions and restricted accounts
#996
Upcoming change: Chain reactions and restricted accounts
We're tightening how Cronicle handles chain reactions for accounts with category or server group restrictions. This closes an authorization gap where an account could use an allowed event to trigger an event outside its permitted scope.
The new rule is straightforward: non-administrator users and API Keys with either kind of restriction cannot initiate chain reactions. This includes success chains, failure chains, and chains requested dynamically by plugins. Having every category or server group in an allowlist does not exempt an account while its restriction remains enabled.
What changes
When a restricted account creates or successfully edits an event, Cronicle permanently sets chain_disabled: true on that event. Its jobs inherit the restriction. An administrator cannot clear it, and later changes to the original account's permissions do not restore chaining.
Restricted accounts also cannot manually run an event with a saved chain. They can run other allowed events, but those jobs receive the restriction without changing the saved event. A successful restricted-account update to a running job flags that job too. If a flagged job updates its source event, that event becomes permanently flagged.
The event editor explains when chain reactions are unavailable and clears old chain settings on save. API requests that configure forbidden chains return an error. Dynamic attempts from plugins are blocked and logged. Normal jobs, progress reporting, and non-chain updates continue to work.
Unrestricted users, API Keys, and administrators can continue to configure chains on unflagged events. A flagged event may still run as the target of an unrestricted chain, but cannot start another chain afterward.
Existing installations
There is no automatic migration. Events saved before this change remain unflagged until a restricted account successfully edits them. Upgrading alone does not disable all previously configured or plugin-generated chains. Changing account permissions alone does not flag existing events or already-running jobs.
Please review events and scripts that restricted accounts could previously edit. Remove unwanted chains and dynamic chain directives, or save an event through a restricted account to apply the permanent flag. Review already-running jobs separately; disabling an event does not stop them.
If an event needs chaining after it has been flagged, an administrator or unrestricted account must review its configuration and create a new event with a new ID. Update integrations and incoming chain references as needed. Keep events that need chaining under unrestricted-account management.
The security documentation explains the complete policy, including API behavior, plugin updates, queues, retries, and upgrade considerations.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Upcoming change: Chain reactions and restricted accounts
We're tightening how Cronicle handles chain reactions for accounts with category or server group restrictions. This closes an authorization gap where an account could use an allowed event to trigger an event outside its permitted scope.
The new rule is straightforward: non-administrator users and API Keys with either kind of restriction cannot initiate chain reactions. This includes success chains, failure chains, and chains requested dynamically by plugins. Having every category or server group in an allowlist does not exempt an account while its restriction remains enabled.
What changes
When a restricted account creates or successfully edits an event, Cronicle permanently sets
chain_disabled: trueon that event. Its jobs inherit the restriction. An administrator cannot clear it, and later changes to the original account's permissions do not restore chaining.Restricted accounts also cannot manually run an event with a saved chain. They can run other allowed events, but those jobs receive the restriction without changing the saved event. A successful restricted-account update to a running job flags that job too. If a flagged job updates its source event, that event becomes permanently flagged.
The event editor explains when chain reactions are unavailable and clears old chain settings on save. API requests that configure forbidden chains return an error. Dynamic attempts from plugins are blocked and logged. Normal jobs, progress reporting, and non-chain updates continue to work.
Unrestricted users, API Keys, and administrators can continue to configure chains on unflagged events. A flagged event may still run as the target of an unrestricted chain, but cannot start another chain afterward.
Existing installations
There is no automatic migration. Events saved before this change remain unflagged until a restricted account successfully edits them. Upgrading alone does not disable all previously configured or plugin-generated chains. Changing account permissions alone does not flag existing events or already-running jobs.
Please review events and scripts that restricted accounts could previously edit. Remove unwanted chains and dynamic chain directives, or save an event through a restricted account to apply the permanent flag. Review already-running jobs separately; disabling an event does not stop them.
If an event needs chaining after it has been flagged, an administrator or unrestricted account must review its configuration and create a new event with a new ID. Update integrations and incoming chain references as needed. Keep events that need chaining under unrestricted-account management.
The security documentation explains the complete policy, including API behavior, plugin updates, queues, retries, and upgrade considerations.
All reactions