And I get this no matter what account I try to reconnect it doesn’t though the connection test worked
Here is what ecwid said: Sorry not sure what documentation you are referring to!
If you mean our API docs, you can check them here: https://api-docs.ecwid.com/reference/overview
In case you are referring to our help articles and guides you can find them here: https://support.ecwid.com/hc/en-us
As for the Pipedream DEV app: such apps are used internally by developers who wish to add custom features to the Ecwid platform and publish their app in our App Market. However, in this case the developer created the app, but didn’t finish the feature development and didn’t proceed communicating with us on publishing the app in our App Market. We usually do not recommend to use such apps, cause we cannot guarantee they will work, as our API team didn’t check them and we do not know how exactly the developer wanted it to work and what scripts they used, etc.
Thanks for the information . We will check on our side and get back to you soon
We’ve added a ticket here: [FEATURE] Ecwid - Publish Pipedream app · Issue #12433 · PipedreamHQ/pipedream · GitHub and added it to Pipedream internal backlog
Thanks for escalating. I am on paid VENTURE and I can add custom apps, which I had done in the past when the connection worked. I then uninstalled them and deleted them and set up a fresh app. I tried reconnecting on several occasions.
Yeah , I think the way forward might be a public app. Where user can install it out of the box.
I’ll also requesting a paid account for testing from ecwid to test your case
That would be a better idea as you would have more users from ECWID. Configuring Pipedream is still a developer oriented (read user unfriendly) system more so than Zapier, and perhaps more than Pabbly also but I believe in Pipedream as it looks like the winner even if it still needs some tweaking.
@Leo any update to the fix? It was working before and no changes were made before June 8 and then it just broke so it can’t be to do with the workflow or the ECWID who have also changed nothing
Hey , no update for now. We will get back to you as soon as there’s any update
Hey , we just pushed an update. Would you mind creating a new Ecwid source to see if it is fixed?
@Leo can I copy the old source or do I have to rewrite it?
Not sure what you mean. You can just add a new Ecwid trigger on your workflow. Delete the old ones
Ok I’ll do that then
no events showing to test new trigger
Could you share the source log if possible? You can access Sign Up - Pipedream, select your source and navigate to Log tab
Is this enough?
end
2024-06-19T13:57:51
error
AxiosError: Request failed with status code 403
at settle (/var/task/node_modules/axios/lib/core/settle.js:19:12)
at IncomingMessage.handleStreamEnd (/var/task/node_modules/axios/lib/adapters/http.js:589:11)
at IncomingMessage.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at Axios.request (/var/task/node_modules/axios/lib/core/Axios.js:45:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async callAxios (/var/task/node_modules/@pipedream/platform/dist/axios.js:110:26)
at async Object.run (<file:///var/task/user/sources/paid-orders/paid-orders.mjs:43:26|file:///var/task/user/sources/paid-orders/paid-orders.mjs:43:26>)
at async /var/task/index.js:122:11
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async exports.main [as handler] (/var/task/index.js:60:20)
Looks like the same error
could you please:
- Go to Sign Up - Pipedream
- Find your newly created trigger and click on it
- Go to the Configuration tab
- Look at the source code and identify what
versionit is at?