Yurutme Gecmisi

Execution history provides a detailed log of every automation run in your project. It shows what triggered each run, which conditions were evaluated, what actions were taken, and whether the run succeeded or failed. Use execution history to monitor your automations, verify they are working as expected, and troubleshoot problems.

Yurutme gecmisini goruntuleme

Kayda erisim

1. Navigate to your project.
2. Go to Settings > Automations.
3. Click the Execution History tab.

The execution log shows recent runs in reverse chronological order (newest first).

Kaydi filtreleme

Use the filter controls to narrow the log:

Filter	Options
Rule	Filter by a specific automation rule
Status	Success, Failure, Partial, Skipped
Date range	Start and end date for the time window
Trigger type	State change, Priority change, Label added, etc.
Work item	Filter by a specific item ID

Calistirma detaylari

Click on any execution entry to see its full details.

Detay alanlari

Field	Description
Run ID	Unique identifier for this execution
Rule name	The automation rule that was triggered
Timestamp	Exact date and time the run occurred
Trigger event	The event that fired the rule (e.g., "State changed to Done")
Work item	The item that triggered the rule (with link)
Triggered by	The user whose action caused the trigger
Conditions checked	List of conditions evaluated and their results (pass/fail)
Actions taken	Ordered list of actions that were executed
Status	Overall run status
Error message	If failed, the reason for the failure
Duration	How long the execution took

Calistirma durumlari

Status	Meaning
Success	All conditions passed and all actions executed successfully
Failure	One or more actions failed to execute
Partial	Some actions succeeded but others failed
Skipped	The trigger fired but conditions were not met, so no action ran

TIP

"Skipped" runs are normal and expected. They mean the automation rule was triggered but the item did not match the conditions. You can use skipped runs to verify your conditions are filtering correctly.

Basarisiz calistirmalarin hatasini ayiklama

When a run fails, the execution detail page shows the specific error that occurred. Common failure reasons and their solutions:

Yaygin basarisizliklar

Error	Cause	Solution
Target state not found	The action references a state that no longer exists	Update the rule to use a valid state
Member not found	The target assignee has been removed from the project	Update the rule with a current project member
Label not found	The referenced label was deleted	Create the label again or update the rule
Permission denied	The automation system lacks permission for the action	Check workspace and project permission settings
Cycle not found	The target cycle was deleted or archived	Update the rule to target an active cycle
Rate limit exceeded	Too many automations fired simultaneously	Reduce the number of overlapping rules
Circular dependency detected	An action triggered another rule that loops back	Review rules for circular trigger patterns

Basarisizligi arastirma

1. Open the failed run from the execution history.
2. Check the Error message field for the specific reason.
3. Review the Conditions checked section to verify the rule targeted the correct item.
4. Check the Actions taken section to see which action failed and where in the sequence.
5. Navigate to the referenced rule and update the configuration.

WARNING

Circular dependencies occur when Rule A's action triggers Rule B, and Rule B's action triggers Rule A. SetGet detects these loops and stops execution to prevent infinite chains, marking the run as "Failed" with a circular dependency error.

Basarisiz calistirmalari yeniden deneme

For runs that failed due to transient issues (e.g., temporary system load), you can retry the execution:

1. Open the failed run detail.
2. Click Retry at the top of the detail page.
3. The system re-evaluates the conditions against the current state of the work item and re-executes the actions.

Yeniden deneme degerlendirmeleri

• Retries use the current state of the work item, not the state at the time of the original failure. If the item has changed since the failure, the retry may produce different results.
• Retries are logged as separate execution entries linked to the original run.
• You cannot retry "Skipped" runs because no action was attempted.

Yurutme gecmisi saklama

Execution history is retained according to your plan:

Plan	Retention period
Free	7 days
Pro	30 days
Business	90 days
Enterprise	Custom
Self-hosted	Configurable

Older entries are automatically purged. If you need long-term audit records, export the execution history before it expires.

Gecmisi disari aktarma

1. Go to the Execution History tab.
2. Apply any desired filters.
3. Click Export to download the filtered history as a CSV file.

En iyi uygulamalar

1. Review regularly — Check execution history weekly to catch silent failures or unexpected behavior.
2. Monitor skipped runs — A high number of skipped runs may mean your conditions are too restrictive or the trigger is too broad.
3. Fix failures promptly — Failed rules are not automatically retried. Unresolved failures mean work items are not being processed as intended.
4. Name rules clearly — Good rule names make the execution log much easier to scan.
5. Avoid overlapping rules — If multiple rules act on the same trigger, review the execution order and check for conflicts.

Ilgili sayfalar

• Automations Overview — Introduction to the automation system
• Automation Rules — Create and configure rules
• Automation Templates — Pre-built rule configurations
• Workflows — Multi-step processes with approval gates