[ECOMMERCE-376] [SF & SAP]Throwing an exception on browser and getting stuck when cannot get access token. Created: 25/Mar/21  Updated: 28/Apr/21  Resolved: 23/Apr/21

Status: Closed
Project: E-commerce
Component/s: None
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Type: Bug Priority: Neutral
Reporter: Thuy To Assignee: Antonín Juran
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
Original Estimate: Not Specified

Attachments: PNG File image-2021-03-25-11-09-28-315.png    
Issue Links:
Cloners
clones ECOMMERCE-371 [Magento] Throwing an exception on br... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Commerce fixes and improvements 1.2.4 - 1.2.5
Sprint: Content Mngmt 02
Story Points: 5

 Description   

Steps to reproduce

  1.  Set up with the instance SF that connection is failed or input the yaml configuration with wrong baseUrl or user/pass.
  2.  Click on SF ecommerce. An exception occurs on browser and get stuck in app.

Expected results

The exception should be shown in log, not thrown on browser and the UI does not get stuck.

Actual results

Workaround

Development notes


Generated at Mon Feb 12 01:43:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.