Timeline for Scratch Org Limit Exceeded, Not Visible In Dev Hub
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2020 at 21:56 | vote | accept | Nathanael Schmolze | ||
| Jan 28, 2020 at 19:22 | comment | added | Nathanael Schmolze | Yeah, me too. I think the idea is that the scratch org record can expire and be deleted, whereas the scratchorginfo record maintains an audit log that is never deleted, for historical purposes (similar to a history table). But personally, I would just give them the same database table, and update a status field. Whatever :-) | |
| Jan 28, 2020 at 3:52 | comment | added | Mitesh | I wonder why scratchorginfo and scratchorg record doesn't have single atomicity to handle this issue. Even limits are based of scratchorginfo per your question. In my case force:org:list followed by force:org:delete has worked like charm always. | |
| Jan 27, 2020 at 22:13 | history | answered | Nathanael Schmolze | CC BY-SA 4.0 |