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
We are currently experiencing a problem where a specific step takes an unusually long time (around 20-30 minutes) to execute and eventually fails. Unfortunately, there are no logs for that particular step in the workflow(UI). Since the failing step is memory-intensive, it is crucial to have access to the logs in order to pinpoint the exact cause of the failure. I would greatly appreciate hearing from anyone who has encountered a similar issue, specifically where a step fails without any available logs, and if there are any recommended solutions to address it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We are currently experiencing a problem where a specific step takes an unusually long time (around 20-30 minutes) to execute and eventually fails. Unfortunately, there are no logs for that particular step in the workflow(UI). Since the failing step is memory-intensive, it is crucial to have access to the logs in order to pinpoint the exact cause of the failure. I would greatly appreciate hearing from anyone who has encountered a similar issue, specifically where a step fails without any available logs, and if there are any recommended solutions to address it.
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions