Skip to content

script can 503 on the URL interrupting playbook run #1

@ninjabong

Description

@ninjabong

First time I tried to run with script I got a 503 error interrupting the playbook run, not sure if there's some way to catch that. Maybe just an ignore_errors: True or catch it with a register and a conditional to prevent it failing on the final update?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions