Skip to content

Commit f5ef8a6

Browse files
committed
Simplify formatting of error message.
1 parent daa8937 commit f5ef8a6

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

pages/pipelines/scheduled_builds.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,20 +10,19 @@ You can also create and manage schedules using the [Buildkite GraphQL API](/docs
1010

1111
## Cron job permission consideration
1212

13-
When setting up a cron job in your parent pipeline, it is important to ensure that the same `Team` has been assigned to the corresponding child pipeline. Failure to match the `Teams` between parent and child pipelines may result an error with the following message:
13+
When setting up a cron job in your parent pipeline, it's important to ensure that the same `Team` has been assigned to the corresponding child pipeline. Failure to match the `Team` between the parent and child pipelines may result in an error with the following message:
1414

15-
<div style="border: 1px solid #e74c3c; background-color: #f9ebec; padding: 10px; border-radius: 5px;">
16-
<p style="color: #c0392b; font-weight: bold;">Error:</p>
17-
<p><span style="color:red"><em>Could not find a matching team that includes both pipelines, each having a minimum "Build" access level.</em></span></p>
18-
</div>
15+
**Error:**
1916

20-
This error is indicative of a mismatch in `Team` assignments, and it highlights the importance of maintaining consistent team configurations across interconnected pipelines to avoid permission-related issues.
17+
_Could not find a matching team that includes both pipelines, each having a minimum "Build" access level._
18+
19+
This error is indicative of a mismatch in `Team` assignments and highlights the importance of maintaining consistent team configurations across interconnected pipelines to avoid permission-related issues.
2120

2221
## Schedule intervals
2322

2423
The interval defines when the schedule will create builds. Schedules run in UTC time by default, and can be defined using either predefined intervals or standard crontab time syntax.
2524

26-
>🚧 Interval granularity
25+
> 🚧 Interval granularity
2726
> Buildkite only guarantees that scheduled builds run within 10 minutes of the scheduled time, and therefore does not support intervals less than 10 minutes.
2827
2928
### Predefined intervals

0 commit comments

Comments
 (0)