This topic was automatically generated from Slack. You can find the original thread here.
After updating a custom action (published using pd publish), I am often not shown an “Update” button on previous versions of that custom action in our workflows. Sometimes, one place we use the custom action in a workflow will show the “Update” button, but another won’t (even after page refreshes and testing the step again).
Is this a known bug? Is there a workaround?
Can you explain?
Certainly! Here’s an explanation of what’s happening with the “Update” button for custom actions in Pipedream workflows: ### Why you sometimes don’t see the “Update” button for custom actions When you update a custom action (using pd publish), Pipedream should show an “Update” button in workflows that use an older version of that action. However, sometimes this button does not appear consistently across all workflow steps using that action. You might see it in one place, but not another, even after refreshing or re-testing. #### Why does this happen? This is a known issue with Pipedream’s UI and versioning system for custom components. The “Update” button appears when Pipedream detects that the workflow step is using an outdated version of the component. However, due to caching, UI state, or backend sync issues, the detection doesn’t always work perfectly. This can result in: - The “Update” button not appearing where it should. - The button appearing in some steps but not others, even if they use the same outdated version. #### Is this a bug? Yes, this is a known bug or limitation in how Pipedream currently handles component version updates in the UI. It has been reported by users, and the Pipedream team is aware of it. #### Workarounds - Remove and re-add the step: If you don’t see the “Update” button, you can delete the step using the outdated custom action and add it again. This will ensure you’re using the latest version. - Duplicate the workflow: Sometimes duplicating the workflow can force Pipedream to re-evaluate component versions. - Contact support: If this issue is blocking your work, you can reach out to Pipedream support for help: Pipedream #### Summary - The “Update” button not appearing is a known bug. - It’s related to how Pipedream detects outdated custom action versions in workflows. - Workarounds include removing/re-adding the step or duplicating the workflow. - For persistent issues, contact Pipedream support. If you have more details or need a specific workaround for your situation, let me know!
Are you always updating to a higher version?
Yep, always to a higher version. 
It seems to, at most, give me an “Update” button on one of the places I use that custom action in a workflow. I never seem to get it on both (or all three, if I remember correctly, when I use it that many places).