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
Copy file name to clipboardExpand all lines: src/tools/report_problem/report_problem.ts
+25-11Lines changed: 25 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -26,23 +26,33 @@ const ACKNOWLEDGEMENT = `Problem reported. Thank you — this helps the Apify te
26
26
exportconstREPORT_PROBLEM_NUDGE=`If you cannot resolve this yourself, report it to the Apify team by calling ${HELPER_TOOLS.PROBLEM_REPORT} (describe what you were doing and this error) before telling the user you could not complete the task.`;
27
27
28
28
/**
29
-
* Failure categories that represent expected, user-resolvable control-flow states (fix input, pay,
30
-
* approve, fix token) rather than genuine Apify defects. The nudge is suppressed for these so it does
31
-
* not flood the channel with paywalls/approvals or steer the agent to give up instead of surfacing the
32
-
* payment/approval URL. `INTERNAL_ERROR` and an absent/unknown category still get the nudge.
29
+
* Softer nudge for INVALID_INPUT failures (payment/standby short-circuits, actor input rejected at
30
+
* runtime, etc.). Most of these are the agent's own mistake, so this doesn't push it to report before
31
+
* giving up — but some are a genuine schema/Actor mismatch the agent would otherwise never think to
32
+
* report, so it still surfaces the tool's existence.
33
+
*/
34
+
exportconstREPORT_PROBLEM_INVALID_INPUT_NUDGE=`If this looks like a bug rather than something fixable by adjusting your request, report it by calling ${HELPER_TOOLS.PROBLEM_REPORT} (describe what you were doing and this error).`;
35
+
36
+
/**
37
+
* Failure categories that represent expected, user-resolvable control-flow states (pay, approve, fix
38
+
* token) rather than potential Apify defects. The nudge is suppressed for these so it does not flood
39
+
* the channel with paywalls/approvals or steer the agent to give up instead of surfacing the
40
+
* payment/approval URL. `INVALID_INPUT` gets the softer {@link REPORT_PROBLEM_INVALID_INPUT_NUDGE}
41
+
* instead of being suppressed outright. `INTERNAL_ERROR` and an absent/unknown category still get the
0 commit comments