You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When running workflows programmatically in payloadcms3, the workflow is executed only once regardless of its success or failure. This behavior leads to no automatic retries even in cases where the workflow fails. This lack of retry mechanism can cause significant issues in production environments where failures are not uncommon and retrying is critical to ensure task completion.
Steps to Reproduce:
Trigger a workflow programmatically using the payloadcms3 API.
Simulate a failure in the workflow (e.g., by introducing an error or returning a failure status).
Observe that the workflow does not retry after the failure.
Expected Behavior:
The workflow should retry according to the configured retry logic or documented behavior, ensuring that transient failures do not lead to permanent task abandonment.
Actual Behavior:
The workflow is executed only once and does not retry regardless of whether it fails.
Hey @denolfe@DracoBlue@colinramsay@jmas , I really could use your help on this since it's a production issue, thanks for everything you do and the great framework!
Describe the Bug
Description:
When running workflows programmatically in payloadcms3, the workflow is executed only once regardless of its success or failure. This behavior leads to no automatic retries even in cases where the workflow fails. This lack of retry mechanism can cause significant issues in production environments where failures are not uncommon and retrying is critical to ensure task completion.
Steps to Reproduce:
Expected Behavior:
The workflow should retry according to the configured retry logic or documented behavior, ensuring that transient failures do not lead to permanent task abandonment.
Actual Behavior:
The workflow is executed only once and does not retry regardless of whether it fails.
Link to the code that reproduces this issue
https://github.com/payloadcms/payload
Reproduction Steps
Steps to Reproduce:
Which area(s) are affected? (Select all that apply)
area: core
Environment Info
The text was updated successfully, but these errors were encountered: