Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Explain what happens when a policy can't be executed by the Orchestrator (e.g. due to errors) #18

Open
phochste opened this issue Oct 14, 2021 · 0 comments
Open

Explain what happens when a policy can't be executed by the Orchestrator (e.g. due to errors) #18

phochste opened this issue Oct 14, 2021 · 0 comments

Comments

@phochste
Copy link
Contributor

There can be many reasons why a policy document can be executed by the Orchestrator.

  • Syntax erros in the document
  • Validation errors in the document
  • Policy functions that are not made available by the orchestrator
  • ServiceHubs that can't be reached within a time limit
  • ServiceHubs that don't return a HTTP 200 or 201
  • ....

What to do in these cases?
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@phochste