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
I think I remember having this discussion and I get why we did this — action ran successfully, with unintended result, vs. action failed to run at all — but in practice I'm finding this is bad UX, because an action failing to have the intended effect is the same thing as the action not running at all in the user's mind and in a practical workflow.
I think we should show some kind of error when an action run doesn't have the expected result — either because it doesn't run at all, or because it didn't have the result the author of the action intended. Very open to how we show and, if needed, distinguish between these errors to the user. It's fine if we don't distinguish at all to the user.
I think I remember having this discussion and I get why we did this — action ran successfully, with unintended result, vs. action failed to run at all — but in practice I'm finding this is bad UX, because an action failing to have the intended effect is the same thing as the action not running at all in the user's mind and in a practical workflow.
I think we should show some kind of error when an action run doesn't have the expected result — either because it doesn't run at all, or because it didn't have the result the author of the action intended. Very open to how we show and, if needed, distinguish between these errors to the user. It's fine if we don't distinguish at all to the user.
This return (
googleDriveImport/run.ts
):Generates this:
The text was updated successfully, but these errors were encountered: