zendesk / zendesk/sunshine-conversations-java
RESTEASY004655 error code when perform the SwitchboardActionsApi.passControl
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Hi, while using the Sunshine API to integrate with our Bot solution. We found there are quite a higher chance the API failed on the SwitchboardActionsApi.passControl . Our sample code as below:
public void passControlConversation(String conversationId, String targetSwitchboardIntegration, @Nullable Map<String, Object> metadata) {
PassControlBody passControlBody = new PassControlBody();
passControlBody.setSwitchboardIntegration(targetSwitchboardIntegration);
passControlBody.setMetadata(metadata);
try {
getSwitchboardActionsApi().passControl(passControlBody, zendeskConfig.getSunshineAppId(), conversationId);
} catch (Exception e) {
log.error(String.format("Sunshine API passControlConversation (%s) exception: %s", conversationId, e.getMessage()));
throw new RemoteServiceException(String.format("Sunshine API passControl conversation (%s) to %s exception: %s", conversationId, targetSwitchboardIntegration, e.getMessage()));
}
}
Our current Sunshine API library version as below:
implementation 'com.zendesk:sunshine-conversations-client:14.2.0'
I cannot find any error code explanations. I suspect this might be related to the Api client connection-pools setting. But we're in the Sandbox environment. There is indeed quite low traffic. I don't think the root cause is because of the concurrency
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at SwitchboardActionsApi.passControl using the reported sunshine-conversations-client 14.2.0 version, then trace how RESTEASY004655 and the API response are surfaced. Reproduce the failure if possible and inspect the client connection-pool settings and sandbox behavior. Done means identifying and documenting the cause and the relevant error-code explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100