Skip to content

Actions: aws-amplify/amplify-backend

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
33,066 workflow runs
33,066 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

e2e_resource_cleanup e2e_resource_cleanup #11111: Scheduled
January 6, 2025 00:31 1m 8s main
main
January 6, 2025 00:31 1m 8s
canary_checks canary_checks #10526: Scheduled
January 6, 2025 00:29 9m 17s main
main
January 6, 2025 00:29 9m 17s
health_checks health_checks #7585: Scheduled
January 6, 2025 00:24 28m 12s main
main
January 6, 2025 00:24 28m 12s
e2e_resource_cleanup e2e_resource_cleanup #11110: Scheduled
January 5, 2025 23:06 59s main
main
January 5, 2025 23:06 59s
canary_checks canary_checks #10525: Scheduled
January 5, 2025 23:06 8m 27s main
main
January 5, 2025 23:06 8m 27s
e2e_resource_cleanup e2e_resource_cleanup #11109: Scheduled
January 5, 2025 22:05 55s main
main
January 5, 2025 22:05 55s
canary_checks canary_checks #10524: Scheduled
January 5, 2025 22:05 9m 2s main
main
January 5, 2025 22:05 9m 2s
e2e_resource_cleanup e2e_resource_cleanup #11108: Scheduled
January 5, 2025 21:05 1m 1s main
main
January 5, 2025 21:05 1m 1s
canary_checks canary_checks #10523: Scheduled
January 5, 2025 21:05 9m 11s main
main
January 5, 2025 21:05 9m 11s
getAmplifyDataClientConfig() fails to check Amplify data variables when API name is defined issue-pending-response #3501: Issue comment #2320 (comment) created by spyderbr6
January 5, 2025 20:37 3s
January 5, 2025 20:37 3s
getAmplifyDataClientConfig() fails to check Amplify data variables when API name is defined issue-pending-response #3500: Issue comment #2320 (comment) created by spyderbr6
January 5, 2025 20:33 2s
January 5, 2025 20:33 2s
e2e_resource_cleanup e2e_resource_cleanup #11107: Scheduled
January 5, 2025 20:06 1m 4s main
main
January 5, 2025 20:06 1m 4s
canary_checks canary_checks #10522: Scheduled
January 5, 2025 20:06 8m 35s main
main
January 5, 2025 20:06 8m 35s
e2e_resource_cleanup e2e_resource_cleanup #11106: Scheduled
January 5, 2025 19:05 1m 25s main
main
January 5, 2025 19:05 1m 25s
canary_checks canary_checks #10521: Scheduled
January 5, 2025 19:05 8m 6s main
main
January 5, 2025 19:05 8m 6s
e2e_resource_cleanup e2e_resource_cleanup #11105: Scheduled
January 5, 2025 18:07 1m 6s main
main
January 5, 2025 18:07 1m 6s
canary_checks canary_checks #10520: Scheduled
January 5, 2025 18:07 8m 35s main
main
January 5, 2025 18:07 8m 35s
health_checks health_checks #7584: Scheduled
January 5, 2025 18:06 5m 52s main
main
January 5, 2025 18:06 5m 52s
validate_cdk_release validate_cdk_release #44: Scheduled
January 5, 2025 18:01 16m 7s main
main
January 5, 2025 18:01 16m 7s
e2e_resource_cleanup e2e_resource_cleanup #11104: Scheduled
January 5, 2025 17:05 57s main
main
January 5, 2025 17:05 57s
canary_checks canary_checks #10519: Scheduled
January 5, 2025 17:05 9m 37s main
main
January 5, 2025 17:05 9m 37s
e2e_resource_cleanup e2e_resource_cleanup #11103: Scheduled
January 5, 2025 16:06 1m 1s main
main
January 5, 2025 16:06 1m 1s
canary_checks canary_checks #10518: Scheduled
January 5, 2025 16:06 8m 26s main
main
January 5, 2025 16:06 8m 26s
validate_cdk_release validate_cdk_release #43: Scheduled
January 5, 2025 16:01 14m 4s main
main
January 5, 2025 16:01 14m 4s
e2e_resource_cleanup e2e_resource_cleanup #11102: Scheduled
January 5, 2025 15:05 1m 4s main
main
January 5, 2025 15:05 1m 4s