This topic was automatically generated from Slack. You can find the original thread here.
until yesterday all relevant events from ECWID were processed by Pipedream correctly. Today not one has been processed at all, as if the trigger isn’t working. No changes have been made since yesterday when it was working. Have you a fix? This is the log:
Error: Request failed with status code 403
at createError (/var/task/node_modules/axios/lib/core/createError.js:16:15)
at settle (/var/task/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/var/task/node_modules/axios/lib/adapters/http.js:269:11)
at IncomingMessage.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
Hey , the HTTP 403 Forbidden error means that the authentication failed, could you visit Sign Up - Pipedream and check if your Ecwid account authentication has broken?
They are suggesting, before close analysis, that it’s the app so I suppose they are stating that it’s a Pipedream issue. In the ECWID pipe dream DEV app code
update from ECWID
Without any context about these errors, our API team are not able to investigate the issue, I’m sorry about that. It’s unclear to us where and on what conditions the errors come up. Still, we looked into the Pipedream app and it turned out that something is going wrong on the installation step: the app can’t receive the neede tokens. So it looks like these errors come from the Pipedream app: the app can’t extract tokens from Ecwid and send correct API requests.
Our API team suggested to uninstall the app and then connect it anew. If it doesn’t work, please contact the Pipedream support and ask them to look into the integration from their side.
Very good question which I may not have enough understanding to answer. The APP is called Pipedream DEV. If you can explain how to answer your question more in detail I will be pleased to stretch my neurons
