Skip to content

Update concepts-pipeline-execution-triggers.md #126451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jasonhorner
Copy link
Contributor

Adding note about Scheduled Trigger DST auto updates. renamed sections and reordered for better usability and flow

Adding note about Scheduled Trigger DST auto updates. renamed sections and reordered for better usability and flow
Copy link
Contributor

@jasonhorner : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 80d6ab8:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/data-factory/author-management-hub.md ⚠️Warning Details
articles/data-factory/concepts-pipeline-execution-triggers.md ⚠️Warning Details
articles/data-factory/control-flow-system-variables.md ⚠️Warning Details
articles/data-factory/how-to-create-custom-event-trigger.md ⚠️Warning Details
articles/data-factory/how-to-create-event-trigger.md ⚠️Warning Details
articles/data-factory/how-to-create-schedule-trigger.md ⚠️Warning Details
articles/data-factory/how-to-create-tumbling-window-trigger.md ⚠️Warning Details
articles/data-factory/how-to-use-trigger-parameterization.md ⚠️Warning Details

articles/data-factory/author-management-hub.md

  • Line 53, Column 203: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#trigger-execution-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

articles/data-factory/concepts-pipeline-execution-triggers.md

  • Line 36, Column 17: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#schedule-trigger-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.
  • Line 263, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

articles/data-factory/control-flow-system-variables.md

  • Line 42, Column 92: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#schedule-trigger-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

articles/data-factory/how-to-create-custom-event-trigger.md

  • Line 171, Column 34: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#trigger-execution-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

articles/data-factory/how-to-create-event-trigger.md

  • Line 157, Column 44: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#trigger-execution-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

articles/data-factory/how-to-create-schedule-trigger.md

  • Line 593, Column 44: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#trigger-execution-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

articles/data-factory/how-to-create-tumbling-window-trigger.md

  • Line 368, Column 3: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#trigger-execution-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

articles/data-factory/how-to-use-trigger-parameterization.md

  • Line 144, Column 42: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#trigger-execution-with-json' in 'articles/data-factory/concepts-pipeline-execution-triggers.md'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

@Court72
Copy link
Contributor

Court72 commented Apr 11, 2025

@dcstwh

Can you review the proposed changes? Note that the validation warnings must be resolved before we can merge.

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Apr 11, 2025
Copy link
Contributor

@jasonhorner : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants