diff --git a/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
index f37718764cf6..f9171dc39cae 100644
--- a/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
+++ b/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
@@ -4,6 +4,8 @@ You can use `jobs.<job_id>.outputs` to create a `map` of outputs for a job. Job
 
 Job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}.
 
+If an output is skipped because it may contain a secret, you will see the following warning message: "Skip output `{output.Key}` since it may contain secret." For more information on how to handle secrets, please refer to the [Example: Masking and passing a secret between jobs or workflows](/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#example-masking-and-passing-a-secret-between-jobs-or-workflows).
+
 To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[AUTOTITLE](/actions/learn-github-actions/contexts#needs-context)."
 
 ### Example: Defining outputs for a job