{"meta":{"title":"Viewing job condition expression logs","intro":"Learn how to access and interpret expression evaluation logs for job-level if conditions in GitHub Actions.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/actions","title":"GitHub Actions"},{"href":"/en/enterprise-cloud@latest/actions/how-tos","title":"How-tos"},{"href":"/en/enterprise-cloud@latest/actions/how-tos/monitor-workflows","title":"Monitor workflows"},{"href":"/en/enterprise-cloud@latest/actions/how-tos/monitor-workflows/view-job-condition-logs","title":"View job condition logs"}],"documentType":"article"},"body":"# Viewing job condition expression logs\n\nLearn how to access and interpret expression evaluation logs for job-level if conditions in GitHub Actions.\n\nWhen a job's `if` condition is evaluated, GitHub Actions logs the expression evaluation to help you understand the result. This is useful for debugging both why a job was skipped and why a job ran when you expected it to be skipped.\n\n## Accessing expression logs\n\n1. Navigate to the workflow run summary.\n2. Click on the job.\n3. Click ****.\n4. Select **Download log archive**.\n5. Extract the ZIP file and open the `JOB-NAME/system.txt` file.\n\n## Understanding the log output\n\nThe system log shows the expression evaluation:\n\n```text\nEvaluating: (success() && ((github.repository == 'octo-org/octo-repo-prod')))\nExpanded: (true && (('my-username/octo-repo-prod' == 'octo-org/octo-repo-prod')))\nResult: false\n```\n\n| Line | Description |\n| -------------- | -------------------------------------------------------------------------------------------------------- |\n| **Evaluating** | The original `if` expression from your workflow file. |\n| **Expanded** | The expression with context values substituted. This shows you exactly what values were used at runtime. |\n| **Result** | The final evaluation result (`true` or `false`). |\n\nIn this example, the expanded line reveals that `github.repository` was `'my-username/octo-repo-prod'` (not `'octo-org/octo-repo-prod'`), which caused the condition to evaluate to `false`.\n\n> \\[!NOTE]\n> Expression logs are only available for job-level `if` conditions. For step-level conditions, you can enable debug logging to see expression evaluation in the job logs. For more information, see [Enabling debug logging](/en/enterprise-cloud@latest/actions/how-tos/monitor-workflows/enable-debug-logging)."}