Workflow isn't attaching for Order Guide even when attach condition is metIssue Workflow is not attached when conditions are matchedCauseThe Script in the user's workflow is updating their custom "u_order_guide" field after insert. Hence, the workflow only attaches once the sc_request record (which the workflow is running on) is updated.ResolutionThe user has an "if" workflow activity in their Service Catalog Request workflow which has a Script inside of it to set their custom "u_order_guide" field.The issue with placing the Script inside of the workflow is that the user's workflow needs the order guide information present upon insert, rather than after, which is what is happening here, and why the current implementation is not working. The value is set after a workflow would already have attached.Engineers in Support are experts in OOB behaviors and specialize in resolving OOB break-fix behaviors. Unfortunately, the debugging and implementing of customizations like this is not in Support's area of expertise.And while Support does not have the expertise to assist in implementing custom code, perhaps something like the following can be attempted: to ensure that the value is present upon insertion of the sc_request record, the user could use a before-insert business rule to pass that value utilizing a Script like the one they already have inside their Service Catalog Request workflow. Then, the user can set the condition on the workflow and it would trigger per expectation as the value would be present when the workflow should attach.The user will just need to be sure to remove the Script from the workflow and place it instead in the Business Rule.