Roboflow async workflows often span multiple runtimes:
HTTP request / Node service -> Pub/Sub -> Python worker -> Pub/Sub -> Node completion handler
Cloud Trace handles a single request boundary, but Pub/Sub breaks that trace. Today, the durable link is usually a domain id embedded somewhere in each payload. In practice, that means an investigation has to know which field each service happened to log: jobId here, autoLabelJobId there, free text somewhere else. The result is brittle multi-clause log archaeology.