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
The message on the execution tab of a Function shows below -
The message isn't 100% accurate though, it should instead be -
Deployment Exists - You have no execution logs. Execute the Function to see see it here.
Deployment Doesn't Exist - Function has no deployment. Create, activate & execute a deployment to see the logs here.
Also, the Execute button shows when there's no deployment & clicking it returns a response from backend - Deployment not found. Create a deployment before trying to execute a function which is fine but this can also be improved with a pre-check of deployment existence.
👍 Expected behavior
Better message should be shown.
👎 Actual Behavior
Message isn't 100% accurate.
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
stnguyen90
changed the title
🐛 Bug Report: [Console|Functions] Improve Message on Execution Tab
🐛 Bug Report: Improve Message on Execution Tab
Oct 10, 2023
👟 Reproduction steps
The message on the execution tab of a Function shows below -
The message isn't 100% accurate though, it should instead be -
You have no execution logs. Execute the Function to see see it here.
Function has no deployment. Create, activate & execute a deployment to see the logs here.
Also, the
Execute
button shows when there's no deployment & clicking it returns a response from backend -Deployment not found. Create a deployment before trying to execute a function
which is fine but this can also be improved with a pre-check of deployment existence.👍 Expected behavior
Better message should be shown.
👎 Actual Behavior
Message isn't 100% accurate.
🎲 Appwrite version
Appwrite Cloud
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: