Not able to identify element getting [WD Proxy] Got an unexpected response with status 404, invalid session

It works fine on pervious appium version, this error is on 1.15.1v.
Here is log from appium. Find it here

I have the same as you. When i try to replay itf file with :

self.driver.execute(Command.W3C_ACTIONS, enc)

Status is 500 for message “appium-base-driver\\lib\\jsonwp-proxy\\proxy.js:261:13)”"

I too have similar issue where i am running my test parallely using TestNG on 2 Andoid Devices ,However i could see the App opening up in both the devices and then oneof the device runs fine until end of execution where the other device stuck and in Appium log i could see that there is no element found . This is happning either way too. sometime working on one device and the other time it isn’tworking on the other one.
Appium Log : (Appium version 1.15.1
[MJSONWP (7832ffad)] Calling AppiumDriver.reset() with args: [“7832ffad-c07c-422e-81ff-29bd4a30a668”]
[ADB] Getting install status for
[ADB] Running ‘D:\sdk\platform-tools\adb.exe -P 5037 -s 226c5f5a0d027ece shell dumpsys package’
[ADB] ‘’ is installed
[ADB] Running ‘D:\sdk\platform-tools\adb.exe -P 5037 -s 226c5f5a0d027ece shell am force-stop’
[ADB] Running ‘D:\sdk\platform-tools\adb.exe -P 5037 -s 226c5f5a0d027ece shell pm clear’
[AndroidDriver] Performed fast reset on the installed ‘’ application (stop and clear)
[ADB] Running ‘D:\sdk\platform-tools\adb.exe -P 5037 -s 226c5f5a0d027ece shell am start -W -n -S’
[MJSONWP (7832ffad)] Responding to client with driver.reset() result: null
[HTTP] <-- POST /wd/hub/session/7832ffad-c07c-422e-81ff-29bd4a30a668/appium/app/reset 200 3516 ms - 76
[HTTP] --> POST /wd/hub/session/7832ffad-c07c-422e-81ff-29bd4a30a668/timeouts
[HTTP] {“type”:“implicit”,“ms”:10000}
[MJSONWP (7832ffad)] Calling AppiumDriver.timeouts() with args: [“implicit”,10000,null,null,null,“7832ffad-c07c-422e-81ff-29bd4a30a668”]
[BaseDriver] MJSONWP timeout arguments: {“type”:“implicit”,“ms”:10000}}
[BaseDriver] Set implicit wait to 10000ms
[MJSONWP (7832ffad)] Responding to client with driver.timeouts() result: null
[HTTP] <-- POST /wd/hub/session/7832ffad-c07c-422e-81ff-29bd4a30a668/timeouts 200 14 ms - 76
[HTTP] --> POST /wd/hub/session/7832ffad-c07c-422e-81ff-29bd4a30a668/element
[HTTP] {“using”:“id”,“value”:“”}
[MJSONWP (7832ffad)] Calling AppiumDriver.findElement() with args: [“id”,“”,“7832ffad-c07c-422e-81ff-29bd4a30a668”]
[BaseDriver] Valid locator strategies for this request: xpath, id, class name, accessibility id, -android uiautomator
[BaseDriver] Waiting up to 10000 ms for condition
[WD Proxy] Matched ‘/element’ to command name ‘findElement’
[WD Proxy] Proxying [POST /element] to [POST http://localhost:8200/wd/hub/session/2908e89c-6b70-49f0-8d05-735d6affa2fe/element] with body: {“strategy”:“id”,“selector”:“”,“context”:"",“multiple”:false}
[WD Proxy] Got an unexpected response with status 404: {“sessionId”:“2908e89c-6b70-49f0-8d05-735d6affa2fe”,“value”:{“error”:“no such element”,“message”:“An element could not be located on the page using the given search parameters”,“stacktrace”:"io.appium.uiautomator2.common.exceptions.ElementNotFoundException: An element could not be located on the page using the given search parameters\n\tat io.appium.uiautomator2.handler.FindElement.safeHandle(\n\tat io.appium.uiautomator2.handler.request.SafeRequestHandler.handle(\n\tat io.appium.uiautomator2.server.AppiumServlet.handleRequest(\n\tat io.appium.uiautomator2.server.AppiumServlet.handleHttpRequest(\n\tat io.appium.uiautomator2.http.ServerHandler.channelRead(\n\tat\n\tat\n\tat io.netty.chann…
[W3C] Matched W3C error code ‘no such element’ to NoSuchElementError
[BaseDriver] Waited for 112 ms so far