Property reference

`com.glide.script.sandbox.ks.watchdog.phase.start`

The com.glide.script.sandbox.ks.watchdog.phase.start property sets a specific date and time for the start of the watchdog phase in the script sandbox. Administrators should review this setting to ensure it aligns with their operational timelines and script execution requirements.

Default: 2026-08-26 06:59:59
Type: string
Application: Global

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	This property defines the start date and time for the watchdog phase in the script sandbox, impacting how scripts are monitored and managed.
What area does it affect?	Script sandbox management
What does the default mean?	The default value is "2026-08-26 06:59:59", which is the baseline setting used unless it is changed.
When should you review it?	Review this property when planning script execution schedules or adjusting monitoring parameters.

Out of the box property record

Raw metadata from the property record.

Property name	`com.glide.script.sandbox.ks.watchdog.phase.start`
Sys ID	`8e491d3683520310f090b0d6feaad356`
Type	string
Application	Global
Default value	`2026-08-26 06:59:59`
Description
Updated	2026-08-26 06:59:59

Sources

Official references and nearby text excerpts where this property appears.

More in `com.glide`

Other properties in the same namespace.

com.glide.script.sandbox.ks.watchdog.auto.advance This property controls whether the system automatically transitions between enforcement phases for guarded scr com.glide.script.sandbox.ks.watchdog.enabled This property determines whether KittyScript is enabled for all transactions, with a default setting that ensu com.glide.script.sandbox.ks.watchdog.phase It defines the enforcement phase for the guarded script evaluator, impacting how untrusted scripts are handled com.glide.script.sandbox.ks.watchdog.phase.duration.days It specifies how long each phase of the KittyScript watchdog remains active before advancing to the next phase com.glide.security.acl.data_condition.run_in_acl_scope This boolean property specifies if data conditions should run in the scope of Access Control Lists (ACLs), imp com.glide.security.acl.record_operations_without_columns It defines a list of ACL Record type operations that do not allow column values, enforcing the use of table va com.glide.security.check_unsanitized_html This property determines how HTML content in translated_html fields is sanitized globally, affecting the secur com.glide.security.oauth.jwt_signing_module_sys_id It defines the cryptographic module for JWT signing, defaulting to the out-of-the-box module.

All 650 properties in com.glide →