Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Decider needs to communicate with SQS #20

Closed
koxon opened this issue Jul 4, 2015 · 1 comment
Closed

Decider needs to communicate with SQS #20

koxon opened this issue Jul 4, 2015 · 1 comment
Assignees

Comments

@koxon
Copy link
Contributor

koxon commented Jul 4, 2015

The decider must send updates to the client through SQS:

  • Workflow started
  • Workflow timeout
  • Errors
    etc.

Without this, there is no way for the client to know about workflow status and possible errors.

You need to integrate the SQS library. The client SQS queue information can be submitted with the JSON payload or in the Plan to determine

@koxon
Copy link
Contributor Author

koxon commented Nov 3, 2015

We experienced today activities aborted by the decider due to timeout.
As the decider doesn't communicate the client application will never be aware of it.

We need to communicate to SQS

@koxon koxon closed this as completed Jan 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants