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
When Payment Widget pays and persists an in-memory request, the resulting Request Scan link shows a "404 Page Not Found" error screen. This is because the storage subgraph has not yet indexed the new request creation due to the Pay before persist flow.
Proposed Solution
Figure out a way to detect if a request or a payment exists but hasn't been indexed yet. If so, display a loading indicator with a retry flow instead of "404 Page Not Found".
Figure out how the "Not Found" page should look for all searches.
The text was updated successfully, but these errors were encountered:
Problem
When Payment Widget pays and persists an in-memory request, the resulting Request Scan link shows a "404 Page Not Found" error screen. This is because the storage subgraph has not yet indexed the new request creation due to the Pay before persist flow.
Proposed Solution
Figure out a way to detect if a request or a payment exists but hasn't been indexed yet. If so, display a loading indicator with a retry flow instead of "404 Page Not Found".
The text was updated successfully, but these errors were encountered: