You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ref(crons): Remove documentation on Attachments (#7867)
Attachments are currently underutilized in the Crons product. As it
stands, the new endpoints (using relay) do not support attachments
easily, so we should avoid documenting this for now.
Copy file name to clipboardExpand all lines: src/platforms/common/crons/index.mdx
-40Lines changed: 0 additions & 40 deletions
Original file line number
Diff line number
Diff line change
@@ -200,46 +200,6 @@ It's important to provide a timezone for non-repeating crontab schedules, such a
200
200
201
201
</Alert>
202
202
203
-
### Check-in Attachment (Optional)
204
-
205
-
Sentry Crons can help you better understand your job check-ins by storing a file, such as a log output. You'll be able to use this to debug check-in failures or track job statuses. To upload your attachment, execute the following `HTTP POST (multipart/form-data)` request:
206
-
207
-
<SignInNote />
208
-
209
-
```bash {tabTitle: curl}
210
-
# Perform a POST request to attach a file to a check-in
We recommend uploading your attachment before you complete your second
232
-
check-in.
233
-
</Note>
234
-
235
-
Attachments can be downloaded in each corresponding check-in on your “Monitor Details” page.
236
-
237
-
Current attachment limitations:
238
-
239
-
1. Each job is limited to one attachment.
240
-
2. The maximum file size is 100kb.
241
-
3. Attachments aren't currently supported by our CLI or SDKs.
242
-
243
203
### Overlapping Jobs (Optional)
244
204
245
205
A job execution that begins before the previous job execution has been completed is called an overlapping job. This happens if you have a job with a runtime duration longer than your job's interval schedule.
0 commit comments