Skip to content
no-response

no-response #352

Sign in to view logs

no-response

no-response #352

Triggered via schedule January 30, 2025 10:08
@unicornwareunicornware
⁠ 200cd09
main
Status Success
Total duration 12s
Artifacts –

no-response.yml

on: schedule
no-response
3s
no-response
Fit to window
Zoom out
Zoom in