This topic was automatically generated from Slack. You can find the original thread here.
Hello Can I please get some help with the errors I’m getting on my workflows?
Thanks
I’m sorry to hear you’re experiencing issues with your workflows. To help you effectively, could you please provide more details about the errors you’re encountering? Information such as the specific error messages you’re seeing, the steps in your workflow where these errors occur, or any patterns you’ve noticed related to when the errors happen would be very helpful. In the meantime, here are a few general steps you can try to troubleshoot the issues: 1. Make a trivial change to your workflow, and Deploy your workflow again. 2. Try searching the community or the pipedream GitHub repo to see if anyone else has solved the same issue. 3. Copy your workflow to see if the issue persists on the new workflow. If you’re still seeing the issue after trying these steps, please reach out in the community for more support. Additionally, if you have an event ID like the one you’ve mentioned (2cgRRs67vLFVQpdecYPW), you can use it to look up specific details about the event and error within your Pipedream dashboard or logs, which might give you more insight into what’s going wrong. Let me know if you need further assistance or if you can provide more details about the errors.
any luck?
I’m here to help, but it seems your question might be missing some details for me to provide a specific answer. Could you please provide more information about what you’re trying to achieve or any specific issue you’re facing with Pipedream? This will help me assist you better.
What is the best way to get in touch with Pipedream support
The best way to get in touch with Pipedream support is by filling out the request form at Support - Pipedream, providing detailed information about your issue.
Every day I am getting around 8 errors on 2 of my workflows.
The first two errors come from this flow:
3. [Daily] Update Labor Hours based on yesterday man-power
The rest of them come from this one:
2. Update Labor Hours for the first time
The first two errors from the 3. [Daily] Update Labor Hours based on yesterday man-power workflow look like this:
TypeError
Cannot read properties of undefined (reading ‘filter’)
at Object.run (file:///pipedream/dist/code/96df26a745745af03fa828fb3fddaf9ca40dd496d753babf2f721802c5e90267/component.mjs:13:28)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at null.executeComponent (/var/task/launch_worker.js:286:22)
at MessagePort.messageHandler (/var/task/launch_worker.js:783:28)
(Get_All_ManPowers)
The other 6 or so errors are for the 2. Update Labor Hours for the first time workflow and the error looks like this:
TypeError
Cannot read properties of undefined (reading ‘items’)
at Object.run (file:///pipedream/dist/code/4cf6429ea226d170c04544f73c3c48a2c48e2b608c1e6530ec5ceee3d718a8bf/component.mjs:9:21)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at null.executeComponent (/var/task/launch_worker.js:294:22)
at MessagePort.messageHandler (/var/task/launch_worker.js:791:28)
(Get_Hours_from_ProEst_and_split_then_in_to_groups)
or this one:
TypeError
Cannot read properties of undefined (reading ‘estimates’)
at Object.run (file:///pipedream/dist/code/53c113ee6fa0fddb4166679f02fa4eb9167f6c3d83913d1d228060da24068e4a/component.mjs:18:42)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at null.executeComponent (/var/task/launch_worker.js:294:22)
at MessagePort.messageHandler (/var/task/launch_worker.js:791:28)
(Find_Project_in_ProEst)
This hasn’t always been the case, from what my coworker (i’m pretty new) this used to work flawlessly.
It seems like the errors you’re encountering in both workflows are related to trying to access properties on an object that is undefined. This typically happens when an expected API response does not contain the data in the format you’re anticipating, or when the response is empty or undefined. For the 3. [Daily] Update Labor Hours based on yesterday man-power workflow, the error message indicates an issue with accessing a filter property. This suggests that the object you’re trying to call .filter on is undefined. Similarly, for the 2. Update Labor Hours for the first time workflow, the errors indicate issues with accessing items and estimates properties. Here are some steps to troubleshoot and potentially resolve these issues: 1. Verify API Responses: Check the API responses immediately before the steps that are failing. Ensure that the data structure returned from the API matches what your code expects. You might need to add checks to ensure the object exists before trying to access its properties. 2. Add Error Handling: Implement error handling to catch cases where data might be missing or in an unexpected format. This can prevent the workflow from failing and allows you to log or handle errors more gracefully. 3. Review Recent Changes: Since you mentioned these workflows used to work flawlessly, review any recent changes to the workflows or the external APIs they interact with. An API’s response structure might have changed, or there could have been changes in the workflow logic. 4. Debugging: Make trivial changes to the workflow and redeploy, as sometimes redeploying can resolve transient issues. Also, consider copying the workflow to see if the issue persists in a new copy. 5. Community and Support: If after these steps the issue persists, 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 facing problems, please reach out in the community for more specific support. Here’s a basic example of adding a check before accessing a property to prevent TypeError: ```
if (response && response.items) { // Your logic here } else { console.log(“Response or items is undefined”); }