{"version":"2.1.310","anchor":"clocksleep-added-to-the-sandbox-call-list","canonical_anchor":"clocksleep-added-to-the-sandbox-call-list","heading":"Sandboxed modules can now pause with a sleep call","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/clocksleep-added-to-the-sandbox-call-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Sandboxed modules can now pause with a sleep call\n\nA sleep call is now available next to the existing time call in a sandboxed module environment\n\n**Unclear.** It is not clear which modules run in this environment, so it is unclear whether you can use it.\n\n**What**\n\nA sandbox is a restricted environment that limits what code can do. In one such environment for modules, a `clock.sleep` call is now available alongside `clock.now`, which was there before.\n\n**Why**\n\nIt lets that code wait for a while, not only read the current time.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}