You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(web): a scheduled run reports to the person who deployed it (CL-8580) (#940)
* test(web): pin the scheduled-run body's person-address wording (CL-8580)
* fix(web): a scheduled run reports to the person who deployed it (CL-8580)
* fix(web): report caught errors resolving the deployer address (CL-8580)
consttask="Do the work your definition describes.";
254
+
if(deployerAddress===undefined){
255
+
return`This is your scheduled run. ${task} Reply with the result.`;
256
+
}
257
+
return`This is your scheduled run. ${task} Mail the result to ${deployerAddress} (pass it as a single-item \`to\` list) with a short, descriptive subject.`;
258
+
}
259
+
260
+
/** The deploying person's mailbox address — same source `session.ts`'s
261
+
* `fetchSession` reads, same shape `threads-api.ts` builds a person
262
+
* participant's address from (`<refId>@<tenantDomain>`). Best-effort: a
263
+
* session probe that fails or comes back signed-out just means the
264
+
* scheduled run's body falls back to naming nobody, never a failed
0 commit comments