Skip to content
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.

resolveIncident is not working #242

Closed
mrsateeshp opened this issue Oct 14, 2021 · 1 comment · Fixed by #243
Closed

resolveIncident is not working #242

mrsateeshp opened this issue Oct 14, 2021 · 1 comment · Fixed by #243
Assignees
Labels
bug Something isn't working

Comments

@mrsateeshp
Copy link
Contributor

zbc.resolveIndecent(incidentKey) is not working, invoking the method reports following error(thrown by gateway):

11:58:32.978 | zeebe | ERROR: [resolveIncident]: 14 UNAVAILABLE: Expected to execute command on partition 0, but either it does not exist, or the gateway is not yet aware of it

having looked at the code, the following snippet appeared to be the culprit, grpc api is expecting json but the below code is passing string.

public resolveIncident(incidentKey: string): Promise<void> {
	return this.executeOperation('resolveIncident', () =>
	   this.grpc.resolveIncidentSync(incidentKey)  //FIXME: this should be {incidentKey: incidentKey}
	)
}
@mrsateeshp mrsateeshp mentioned this issue Oct 14, 2021
@jwulf jwulf added bug Something isn't working and removed triage labels Oct 19, 2021
@jwulf jwulf self-assigned this Oct 19, 2021
@jwulf jwulf closed this as completed in #243 Dec 5, 2021
@jwulf
Copy link
Member

jwulf commented Dec 7, 2021

Version 1.3.5 has been published with this patch in it.

Thank you for your contribution!

@jwulf jwulf changed the title resolveIndecent is not working resolveIncident is not working Dec 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants