Closed ybudamala closed 3 years ago
As discussed with @GangamRitesh earlier, looks like all inputs are not being sent to the SDK as per initial analysis. Need to check the same issue again on the customer tenant if the instance is available to debug the issue.
Issue is reproducible internally:
https://app.workato.com/recipes/1457752#recipe
https://applaud-dev-com.applaudhcm.com/new-order
https://applaud-dev-com.applaudhcm.com/models-schema/5fec2054754e644a0ae54a40
This issue seems happening because record is getting created instantly in Mongo DB but not in Elastic. But when update is happening on the same record - throwing 404 error.
Looks like same issue raised in cloud board - https://github.com/ApplaudSolutions/applaud-cloud/issues/2533
This is not an issue with Applaud Workato connector. Cloud api is returning the 404 response since it is unable to find the record.
@vinaykumarkasireddy yes..record is not getting indexed onto elastic upon creation instantly. Closing this.
Describe the bug When a recipe is designed with Applaud connector, Create action is going fine. But Update action is failing with 404 error.
Steps to reproduce
404 Not Found: {"data":{"messages":[{"mood":"assertive","timeout":120000,"text":"Oops, something’s not right","body":"You did not have UPDATE permissions for one or more of the resources updated","stack":"Error: You did not have UPDATE permissions for one or more of the resources updated\n at setArgs.then.then.then.then (/data/workspace/applaud-
Expected behavior Should be able to perform UPDATE action without any errors
Screenshots
URL Will be shared through call
Additional context Will be shared through call
Developer Testing
Requestor: leave this section blank Developer: complete this section during commit/pull request
Positive testing:
Add all the things that you have checked whilst completing this story here, it should be written in a non-technical way, and a lot of this can probably be taken from the acceptance criteria, here are two different examples:
Negative testing:
Here you list the things you have checked where your code needs to show an error, handle unusual/bad input/config gracefully, or may impact separate features that use or depend on the same code. Pause and think -- they may not be obvious! Examples:
e2e test links and description: