The upstream fallback (#20) forwards the caller's own token. A local user whose token was never a real Apify credential gets a 401 from the platform, which fails closed to the original local error — exactly as designed.
The result is that fallback looks switched on and does nothing, with no signal anywhere except a line in the runtime's log. A developer who enabled it and sees their call still failing has no way to tell whether the platform lacks the resource or their token was never valid.
The console knows whether a user resolved against the platform at creation time, so /settings could say so.
Follow-up named in that change's design.
The upstream fallback (#20) forwards the caller's own token. A local user whose token was never a real Apify credential gets a
401from the platform, which fails closed to the original local error — exactly as designed.The result is that fallback looks switched on and does nothing, with no signal anywhere except a line in the runtime's log. A developer who enabled it and sees their call still failing has no way to tell whether the platform lacks the resource or their token was never valid.
The console knows whether a user resolved against the platform at creation time, so
/settingscould say so.Follow-up named in that change's design.