This topic was automatically generated from Slack. You can find the original thread here.
@Pi why is only one test event showing in the ecwid-paid-orders configuration dialog
It seems you’re not correctly mentioning Pi
why is only one test event showing in the ecwid-paid-orders configuration dialog
It sounds like you’re experiencing an issue with the Ecwid Paid Orders trigger configuration dialog in Pipedream, where only one test event is showing. This could be due to several reasons: 1. Limited Test Data: If there are only a few recent paid orders in your Ecwid store, you might only see one test event. Ensure that there are multiple recent paid orders in your store. 2. Max Days Back Setting: The “Max Days Back” setting in the trigger configuration determines how far back the trigger should look for orders. If this is set to a low number, it might limit the number of test events. Try increasing this value. 3. Order Fulfillment Status: The “Set order fulfilment status” and “New Fulfilment Status” settings might also filter out some orders. Ensure these settings are configured correctly to include all relevant orders. Here are the steps to configure the Ecwid Paid Orders trigger: ## How do I use the New Ecwid Paid Orders trigger? 1. Search for the ecwid app from the trigger menu. 2. Select the New Ecwid Paid Orders trigger. 3. Connect your ecwid account. 4. Select a Max Days Back or pass an integer from a previous step. 5. Select a Set order fulfilment status (Preferred) or pass a boolean from a previous step. 6. Select a New Fulfilment Status or pass a string from a previous step. 7. Follow the instructions on the trigger configuration screen. You may need to generate a test event from ecwid to get real data to test your workflow. If you’ve checked these settings and still only see one test event, it might be helpful to generate additional test orders in your Ecwid store to see if they appear. If you continue to experience issues, please visit Support - Pipedream for further assistance.
I have sent a support ticket since I had no response regarding this on this channel after several attempts at reporting this issue.
Yes I did all that and there is still only one test event in my now apparently working workflow (thanks for that) and often when configuring a trigger NO test event show at all and it just hangs waiting.
so the ecwid pipedream workflow is deployed and reported as functioning and the trigger is set correctly to every 5 minutes, 2000 days back, set order fulfillment status TRUE and set to DELIVERED, only one order shows under “select different event” and above all the trigger isn’t triggering. What’s wrong with this and how do I fix it.
I’m sorry to hear you’re having trouble with your Ecwid workflow. Let’s try to troubleshoot this step-by-step. ### Steps to Troubleshoot 1. Check Workflow Deployment: - Ensure that your workflow is deployed. Sometimes, even if the workflow is reported as functioning, it might not be deployed correctly. Make a trivial change to your workflow and deploy it again. 2. Verify Trigger Configuration: - Double-check the configuration of your trigger. Ensure that the settings for “Max Days Back,” “Set order fulfillment status,” and “New Fulfillment Status” are correctly set. 3. Generate Test Events: - Sometimes, generating a test event from Ecwid can help in identifying issues. Follow the instructions on the trigger configuration screen to generate a test event. 4. Check Logs: - Look at the logs for your workflow. They can provide insights into why the trigger isn’t firing. You can find logs in the Pipedream UI under your workflow’s “Logs” tab. 5. Community and Support: - If the above steps don’t resolve the issue, try searching the Pipedream community or the Pipedream GitHub repo to see if anyone else has encountered and solved a similar issue. - If you’re still seeing the issue after trying these steps, please reach out in the Pipedream community. ### Specific Configuration for Ecwid Trigger Here’s a quick reminder of how to set up the Ecwid Paid Orders trigger: 1. Search for the Ecwid app from the trigger menu. 2. Select the New Ecwid Paid Orders trigger. 3. Connect your Ecwid account. 4. Select a Max Days Back or pass an integer from a previous step. 5. Select a Set order fulfillment status (Preferred) or pass a boolean from a previous step. 6. Select a New Fulfillment Status or pass a string from a previous step. 7. Follow the instructions on the trigger configuration screen. You may need to generate a test event from Ecwid to get real data to test your workflow. If you have followed these steps and the issue persists, please provide more details or screenshots of your configuration so I can assist you further. For more detailed information, you can refer
so I did all that and now the workflow reports deployable but when deployed it doesn’t work (even after changing the workflow nominally and redeploying) and only one test event is showing instead of thousands. So after 3 weeks we are nearly there but I have no idea as to what caused this nor if it will be ever fixed at this point as itngets ever more mysterious
have you seen my last email regarding the storeId and secret_token? I was testing some other API routes and couldn’t retrieve the profile information from your store using your storeId and secret_token. I am still getting the Forbidden error.
Hi, just saw it now and replied. I also have four different apps on ECWID with 4 different secret tokens so you want me to send them all? The code I used when the connection was working was the app numbered #4
I responded there
@U03CXTHK4RF thanks very much for your efforts. It appears to work now though it is still not possible to go back more than a few (maybe 6) test events notwithstanding @Pi’s “fix”. What was the issue that caused the workflow to break? I would also like to ask how to reference in Sheets the ECWID data coming from a new “show in payments” field. The column header is “anschlussland_insurance” and I tried {{steps?.trigger?.event?.anschlusslandInsurance}} in the relative Sheets workflow component field, but the data is not pulled into Sheets. Ideas?
Hey , I’m not sure I catch what you mean
which part didn’t you get?
I would also like to ask how to reference in Sheets the ECWID data coming from a new “show in payments” field. The column header is “anschlussland_insurance” and I tried {{steps?.trigger?.event?.anschlusslandInsurance}} in the relative Sheets workflow component field, but the data is not pulled into Sheets. Ideas?
Ok so I am using custom checkout fields in the email page and they should output content like the ones I use already in the checkout page
The data does’t appear though it’s in ECWID csv sorry it the cvs output by exporting data the column called surcharges contains the data I need so I cleared the headings and reset them and put this in the surcharges box {{steps?.trigger?.event?.surcharges}} but still no joy ECWID says Thanks for the details. As I see, the column has correct values
Seems like there is an issue with the app itself
Pipedream app - it was developed by third-party developers
So I would recommend to reach out to them at oauth@pipedream.com
Do you have a specific event ID in Pipedream I can open to look at?
This happens all the time since these custom fields have been implemented some days ago. Where do I find an event ID?