Skip to content
DPC - Smoke Test

DPC - Smoke Test #199

Sign in to view logs

DPC - Smoke Test

DPC - Smoke Test #199

Manually triggered March 6, 2026 16:21
@jdettmannnavajdettmannnava
⁠ 8052ef8
jd/dpc-5222-pace-smoke-tests
Status Success
Total duration 2m 21s
Artifacts –

smoke-test.yml

on: workflow_dispatch
Smoke Test
1m 30s
Smoke Test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Smoke Test
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
Smoke Test
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
Smoke Test
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
Smoke Test
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.