search

forcedotcom / code-builder-feedback

This repository is used to collect feedback for the Code Builder beta.
29 stars 2 forks source link

Hour Limit Consumed by Environment Creation? #158

Closed jkranz-rk closed 2 years ago

jkranz-rk commented 2 years ago

What is your role?

Platform Product Manager

What do you normally work on when building on the Salesforce Platform?

OEM Application

What tools do you use today to develop on the Salesforce Platform?

VSCode, Dev Console

How do you see Code Builder fitting into your current workflow? Will it replace any tools you are currently using?

Unsure yet

General feedback

Wasn't sure whether this is a bug or feedback: I noticed the 20 hour limit starts ticking while an environment is getting created. Is that correct? If that is by design, my feedback is that the amount of time it takes to create an environment seems out of our control, and hard to understand why that would count against usage time. If that isn't by design, let me know, I can re-submit this as an Issue.

See the screenshot below, my first environment is still being created, never accessed, and my usage time is getting consumed:

image

Insouciance commented 2 years ago

This is quite frustrating. Environment creation is currently > 30 minutes for my org and still running with no signs or indications of when it might complete. It seems unfair to have this time counted against usage.

smaddox-sf commented 2 years ago

Hi @jkranz-rk and @Insouciance - Your startup experience is not what we’re aiming for. Did both of your Code Builder environments load eventually? Do you still have timing remaining?

github-actions[bot] commented 2 years ago

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.